configure: WARNING: libc does not have argp checking for argp_parse in -largp... no configure: error: no libargp found !!! Please attach the following file when seeking support: !!! /var/tmp/portage/dev-libs/elfutils-0.178/work/elfutils-0.178-abi_x86_64.amd64/config.log ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-20200311-204810 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-gentoo-linux-musl-9.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Wed, 11 Mar 2020 23:38:57 +0000 emerge -qpvO dev-libs/elfutils [ebuild N ] dev-libs/elfutils-0.178 USE="bzip2 nls utils -lzma -static-libs -test (-threads) -valgrind"
Created attachment 618228 [details] emerge-info.txt
Created attachment 618230 [details] dev-libs:elfutils-0.178:20200312-002245.log
Created attachment 618232 [details] emerge-history.txt
Created attachment 618234 [details] environment
Created attachment 618236 [details] etc.portage.tbz2
Created attachment 618238 [details] logs.tbz2
Created attachment 618240 [details] temp.tbz2
Yeah, upstream elfutils does not really work on musl, bug #602126 has a few more issues.
We now depend on it in the ebuild and the build system seems to pick it up fine nowadays.