#GCC build failure

1 messages · Page 1 of 1 (latest)

halcyon oracle
crisp bobcat
#
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.

halcyon oracle
halcyon oracle
#

Okay, bumping issue

halcyon oracle
#

@night aurora nah man, with LLVM_SLOT="18" is still fails with llvm 19 ranlib

#

Im doing it with amd64 keyword then

halcyon oracle
#

DAFUK

#

IT FAILS WITH THE SAME ERROR EVEN ON FORCED LLVM 18

night aurora
#

just fun with experiments :)

halcyon oracle
#

Nah man im movin back

#

It randomly decided to go "nuh uh im not working" mode

night aurora
#

mixed abi fun can become especially fun

#

often resolvable if there is a missing 32bit package however

halcyon oracle
#

That error was from different (hardened) gentoo installation, and it was specifically clang's error - i built gcc successfully using gcc

night aurora
#

ahh ok :)

halcyon oracle
#

But i hate this thing so much already

#

Im gonna migrate to gcc profile lmao

halcyon oracle
#

Ranlib spotted

halcyon oracle
#

Bumping issue

halcyon oracle
#

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.

halcyon oracle
#

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

spiral relic
#

Needs to be reported as a bug

#

A compiler expert is what you need here

halcyon oracle
halcyon oracle
spiral relic
#

Yep report

#

Make sure the reproduce steps are included

halcyon oracle
#

Okay