Building FreeBASIC 1.06 Release

[MrSwiss]

The direct download link is http://www.godevtool.com/Gorc.zip and in theory should give you the same issue, unless the file was compromised by its brief visit to my build system.

Thanks for the link, this worked without problems (no message from Avira).
It seems, it's related to the build process, after all ...

[coderJeff]

It seems, it's related to the build process, after all ...

Indeed, thanks. I see now: the build script gets a clean copy of GoRC.exe from the website, but then runs strip command on all exe's and GoRC.exe is getting modified. Don't think need to be alarmed about this, but also don't want this to happen. I'll fix that for next release. Thanks.

[deltarho[1859]]

In case anyone is curious, about 8 hours of building packages and about 5 hours of uploading files so far, plus last 2 months :)

A labour of love comes to mind.

Thank you and very well done!

[Provoni]

Thanks allot to CoderJeff and the FreeBASIC team and everyone else involved in 1.06!

I've tested the 64-bit release on my software, AZdecrypt, having almost 50.000 lines and there were no problems.

What gcc is used and is there a link that shows what compiler switches are available? Mainly need to know the CPU architectures the gcc supports.

[k6sti]

I installed FreeBASIC-1.06.0-win32.exe on my WinXP system. Avast reported that uninstall.exe had FileRepMalware. When I sent uninstall.exe to virustotal.com, AVG reported "FileRepMalware," McAfee-GW-Edition reported "BehavesLike.Win32.Ransom.lc," and SentinelOne reported "static engine - malicious." 1.06 generated working code, but the full-screen command line kept switching to the desktop during compilation. I deleted everything without using uninstall.exe.

Brian

[coderJeff]

You can use the ".zip" version which should give no issues with the anti-virus. We are using NSIS (nullsoft installer) to create our self extracting installer. I am thinking, it is most likely a false positive, which evidently, NSIS is known for. See https://nsis.sourceforge.io/NSIS_False_Positives
I can reproduce the issue here (I am also using AVAST), and the installer exe is blocked when I try to run. I have reported it as a false positive. Though I don't how long it takes for it get added to the virus definitions.

For fbc.exe switching to full screen problem, maybe try the mingw-org build of the compiler, not sure about that one. I can't remember last time I ran console in fullscreen on windows, so maybe worth some investigation on all versions. Thanks.

[coderJeff]

What gcc is used and is there a link that shows what compiler switches are available? Mainly need to know the CPU architectures the gcc supports.

If you are using standalone version of fbc.exe you can find gcc in the bin/win64/gcc.exe which should be version 7.1.0.
You can check by running 'gcc --version'.
And 'gcc --target-help' will give a list of all the target specific command line options (llike -m32, -m64, etc).
For link to all options see https://gcc.gnu.org/onlinedocs/gcc-7.1.0/gcc/

If you are using the normal version of fbc.exe, installed in to your host build environment, then fbc should use whatever version of gcc is in your host build environment.

[k6sti]

I tried the .zip archive. The compiler will not run without a floppy disk in A:. Then I tried FreeBASIC-1.06.0-win32-mingworg.zip. Executing the compiler yielded an error message that libiconv-2.dll was not found. I am using WinXP Pro version 2002 Service Pack 3.

Brian

Edit - At the full-screen command line, the mingworg FB generated an error message that as.exe was not found in ...\bin\win32.

[coderJeff]

The compiler will not run without a floppy disk in A:.?? What shell are you running in?

On WinXPSp3 Home from cmd.exe shell. 'set PATH=' and just run fbc.exe:
FreeBASIC-1.06.0-win32.zip works OK for me
FreeBASIC-1.06.0-win32-mingworg.zip works OK for me

Not sure what to suggest next.

[k6sti]

I am using cmd.exe. The mingworg also complains if there is no floppy drive in A:. If I put one in the drive and enter fbc with no parameters, the floppy light comes on, the screen reverts to the desktop with no error message, and the options are listed at the command line as expected.

I can continue to use 1.05. I just wanted to post this in case anyone else has the same problem.

Brian

Edit - Here is the mingworg error message from the command line. I think my previous message may have implied that as.exe itself was missing. I can see it in ...\bin\win32\.

C:\x\coil>fbc -lang qb -t 32 -a casm.obj coil.bas icon.res
coil.bas() error 91: Executable not found: "c:\progra~1\freeba~1\bin\win32\as.exe"

[Lost Zergling]

coderJeff, a lot of work, I suppose, thank you for this lattest release.

[counting_pine]

For reference, here's a link to an online scan for uninstall.exe: https://www.virustotal.com/#/file/7bb6c ... /detection

Brian, I wonder if it's worth checking your environment for references to 'A:'

Code: Select all

set | findstr A:

Maybe also check the directory listing of the bin\win32 directory:

Code: Select all

dir /a /s "c:\progra~1\freeba~1\bin\win32\"

[k6sti]

Interesting that the online scan lists two more hits than mine did yesterday.

No environment references to A:.

Directory listing yielded this (mingworg version):

Directory of c:\progra~1\freeba~1\bin\win32

02/20/2019 03:33 AM <DIR> .
02/20/2019 03:33 AM <DIR> ..
02/20/2019 03:33 AM 112,142 libgcc_s_dw2-1.dll
02/20/2019 03:33 AM 131,598 zlib1.dll
02/20/2019 03:33 AM 913,934 ar.exe
02/20/2019 03:33 AM 1,643,022 as.exe
02/20/2019 03:33 AM 944,654 dlltool.exe
02/20/2019 03:33 AM 6,263,511 gdb.exe
02/20/2019 03:33 AM 58,880 GoRC.exe
02/20/2019 03:33 AM 946,702 gprof.exe
02/20/2019 03:33 AM 1,206,798 ld.exe
9 File(s) 12,221,241 bytes

Brian

[Lost Zergling]

@Brian. "..the online scan lists two more hits than mine did yesterday." Maybe not from FB. Maybe you got a hook in kernel triggered by cmd.exe XPSP3 is no longer supported by the lessor tied selling software.

[counting_pine]

For what it's worth, my own build also produced an uninstaller with false positives (using NSIS 3.04).

Here's a mingw-64 issue that might be helpful with regards to floppy drive access?
https://sourceforge.net/p/mingw-w64/bugs/133/