https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: sys-libs/pkgcraft-0.0.13 fails to compile. Discovered on: amd64 (internal ref: tinderbox_musl) System: MUSL-SYSTEM Info about the system: https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#MUSL Info about the issue: https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#CF0014
Created attachment 883347 [details] build.log build log and emerge --info
Error(s) that match a know pattern in addition to what has been reported in the summary: thread 'main' panicked at /var/tmp/portage/sys-libs/pkgcraft-0.0.13/work/pkgcraft-c-0.0.13/vendor/bindgen/lib.rs:620:31: Error: CliError { error: Some(1 job failed), exit_code: 101 } error: failed to run custom build command for `scallop v0.0.12`
This is more of a Gentoo clang issue (on musl) then a pkgcraft one, if you're building rust code using cbindgen against musl you need a static clang library on the system as seen by the following message in the build log: Unable to find libclang: "the `libclang` shared library at /usr/lib/llvm/17/lib/libclang.so.17.0.6 could not be opened: Dynamic loading not supported" Therefore, the clang ebuild should build and install the libclang.a static library on musl targets if it wants to be usable on them.
I forgot to mention as proof of pkgcraft et al. building fine on musl systems: upstream provides static binaries built using musl for the tool related projects (see https://github.com/pkgcraft/pkgcraft/releases), but not pkgcraft-c (sys-libs/pkgcraft) because currently it makes little sense to provide that for musl targets.
See also bug 915651 (which is, confusingly, being used for two issues).
