glibc 2.14 was released 2011-06-01. IMO I think 4 1/2 years back-compatibility (when released in early 2016) is much too little; the Windows build probably works on OSes at least 17 years old.
There are good (but not strongly compelling) reasons not to statically link glibc, which I got into in a recent thread on static linking.
casein wrote: Apparently there is also a way to generate intermediate C code on a different machine and use that to build the compiler using just GCC on your target machine.
It's really easy! All you need is gcc and basic libraries like curses!
Just download https://sourceforge.net/projects/fbc/fi ... z/download
Then extract it and run
Code: Select all
make -j4 bootstrap
make install prefix=~/local/fb-1.05
or wherever you want to install it. Or put it in /usr or /usr/local so that you don't even need to update $PATH. Done.
(Note: you have to install it, it won't run properly without because of the path to the 'inc' directory)
It's a bit analogous to a Windows app requiring a more recent version of MSVCRT.dll than your operating system supports.
Mostly. But any Windows program that depends on some certain version of mscvrt.dll (other than the one that's been present on all Windows OSes for 20 years*) but doesn't include it is simply broken. That's quite different to Unix where libc is truly a core part of the OS which evolves.
*there are newer builds of this old version shipped with newer OSes, but they are just minor updates and not comparable to the modern versions of mscvrt_*.dll shipped with Visual Studio.