Summary: | dev-libs/libsecp256k1 fails to compile without GCC installed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Luke-Jr <luke-jr+gentoobugs> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 408963 | ||
Attachments: |
build.log
other.tar.bz2 |
Description
Agostino Sarubbo
2020-06-27 14:15:31 UTC
Created attachment 646790 [details]
build.log
build log and emerge --info
Created attachment 646792 [details]
other.tar.bz2
other logs
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...? FTR gcc is installed here, I'm just using clang by setting the relative env variables. (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? (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" |