mandian wrote: ↑Mar 11, 2024 23:30
sed ...
I believe all the other uses for "lib" are for naming output files, e.g. "lib" + "SOMENAME" + ".a", etc. I can see how would seem to work ok when producing an executable only.
so definitively gcc 13 changed something.
Yes, I think default is a newer standard. I'm not sure what the changes in the standard create issues ... I seen this before, but at the moment I can't recall where and why I had to specify a different stdc. I may remember, .. or not, lol.
clang[\i] fails with the bootstrapped fbc code
Actual support for clang has been added only recently to fbc 1.20.0
We added '-gen clang' command option to generate c backend code that is better compatible with clang
tmc included a patch for the indirect goto error in his work when adding the clang support:
https://github.com/freebasic/fbc/commit ... 725cb521d6
I appreciate you sticking with it and trying to get things to work. Sounds like you will probably need the clang addition in fbc 1.20.0 to get bootstrapped with more suitable clang sources.
Which reminds me that I never tagged fbc version 1.10.2, which is already merged to fbc/master and it includes a new makefile option BOOTFBCFLAGS to pass extra options when building the bootstrap distro.
If you wanted to test just the new clang stuff, but not the newest current development:
You could try creating a bootstrap with commit # a40bb40b055d0dac54fb5ee6c6eeb517a1bae553 from fbc/master
You may need to patch the makefile to use '-gen clang' when partial compiling the fbc sources.
If this works for you, maybe we could do a 1.10.3 partial release and post your bootstrap sources.