Unsure if this is actually common to all hardware, trying some other flavors as I write this, but on a gentoo aarch64-unknown-linux-gnu system emerging sys-fs/lvm2::musl with an aarch64-unknown-linux-musl cross-toolchain the build fails with undefined references to rpl_malloc and rpl_realloc A fix/workaround I've found is to set (either in the ebuild's src_configure or via pkg.env) ac_cv_func_malloc_0_nonnull=yes and ac_cv_func_realloc_0_nonnull=yes Unsure where such a fix should be made, either in sys-devel/crossdev's site files or maybe in the ebuild itself (I've seen it/similar hacks in a lot of in-tree ebuilds). Other info inbound as I un'fix' it and rerun builds to capture logs and such.
Created attachment 560930 [details] build.log
Created attachment 560932 [details] aarch64-unknown-linux-musl-emerge --info
Created attachment 560934 [details] emerge --info (native aarch64-unknown-linux-gnu)
I guess it would help to see config.log if it's dependent on ./configure output. My guess would be that checking for GNU libc compatible malloc... no is a relevant piece.
(In reply to Sergei Trofimovich from comment #4) > I guess it would help to see config.log if it's dependent on ./configure > output. > My guess would be that > checking for GNU libc compatible malloc... no > is a relevant piece. Exact same failure on an x86_64-pc-linux-gnu->x86_64-pc-linux-musl cross
