#GCC build failure
1 messages · Page 1 of 1 (latest)
14.2.1_p20240921/work/gcc-14-20240921/libgcc/config/i386/avx_resms64.S
cc1: error: ‘-fcf-protection’ is not compatible with this target
-fcf-protection is only available on x86_64 arch, but it looks like you are using x86 arch.
Has been fixed, i needed to use GCC for building hardened GCC, instead of LLVM
Okay, bumping issue
GCC fails to build on LLVM profile. Log: https://0x0.st/X0dm.log , portage info: https://bpa.st/QPW7U
@night aurora nah man, with LLVM_SLOT="18" is still fails with llvm 19 ranlib
Im doing it with amd64 keyword then
just fun with experiments :)
@halcyon oracle which abi use flags do you have enabled?
mixed abi fun can become especially fun
often resolvable if there is a missing 32bit package however
I dont have any abi use flags set explicitly
That error was from different (hardened) gentoo installation, and it was specifically clang's error - i built gcc successfully using gcc
ahh ok :)
Ranlib spotted
Bumping issue
Issue: gcc compilation fails because llvm-ranlib doesn't accept flag --plugin (llvm profile). It indeed doesn't accept it, because llvm-ranlib is a symlink to llvm-ar. However, even if i use gcc-fallback env overriding path to ranlib, it still fails.
I have an idea!
Im dumb
gcc-fallback env sets RANLIB to ranlib, but default ranlib is llvm's one
So i need to use gcc-ranlib there
But stil, why tf it doesn't like llvm's ranlib
Yes, now i see it using gcc-ranlib
Oh, hm, llvms ranlib is not a symlink to llvm-ar
But it really doesn't have --plugin flag
You think so? Okay, i will prepare info for that
I cant compile even gcc 13 because of the same issue
Okay