Bug 729888 – dev-libs/libsecp256k1 fails to compile without GCC installed

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Agostino Sarubbo 2020-06-27 14:15:31 UTC]

@@This is an auto-filed bug@@
Feel free to change the summary at your convenience.

Issue: dev-libs/libsecp256k1 fails to compile.
Discovered on: amd64

NOTE:
This machine uses a clang/LLVM toolchain.
If you think that this issue is strictly related to clang/LLVM please mention it in the summary and block bug 408963. If you need further logs, feel free to ask.

[Comment 1 Agostino Sarubbo 2020-06-27 14:15:38 UTC]

Created attachment 646790 [details]
build.log

build log and emerge --info

[Comment 2 Agostino Sarubbo 2020-06-27 14:15:42 UTC]

Created attachment 646792 [details]
other.tar.bz2

other logs

[Comment 3 Luke-Jr 2020-06-27 19:26:41 UTC]

This is using AX_PROG_CC_FOR_BUILD to determine the correct compiler to target the build system (in case of cross compiling). This is needed because it runs custom code at build time to pre-generate data for the final library.

How are other packages that use AX_PROG_CC_FOR_BUILD being fixed? I don't see any commits upstream relating to clang...?

[Comment 4 Agostino Sarubbo 2020-06-30 09:03:04 UTC]

FTR gcc is installed here, I'm just using clang by setting the relative env variables.

[Comment 5 Luke-Jr 2020-06-30 11:22:00 UTC]

(In reply to Agostino Sarubbo from comment #4)
> FTR gcc is installed here, I'm just using clang by setting the relative env
> variables.

Must not be in PATH or something?

[Comment 6 Agostino Sarubbo 2020-06-30 12:10:58 UTC]

(In reply to Luke-Jr from comment #5)
> (In reply to Agostino Sarubbo from comment #4)
> > FTR gcc is installed here, I'm just using clang by setting the relative env
> > variables.
> 
> Must not be in PATH or something?

yes, I have gcc-config with USE="-native-symlinks"