https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: x11-terms/alacritty-0.13.2 fails to compile. Discovered on: amd64 (internal ref: tinderbox_musl) System: MUSL-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 899769 [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: /usr/lib/gcc/x86_64-pc-linux-musl/14/../../../../x86_64-pc-linux-musl/bin/ld: cannot find -lexpat: No such file or directory /usr/lib/gcc/x86_64-pc-linux-musl/14/../../../../x86_64-pc-linux-musl/bin/ld: cannot find -lfontconfig: No such file or directory /usr/lib/gcc/x86_64-pc-linux-musl/14/../../../../x86_64-pc-linux-musl/bin/ld: cannot find -lfreetype: No such file or directory = note: /usr/lib/gcc/x86_64-pc-linux-musl/14/../../../../x86_64-pc-linux-musl/bin/ld: cannot find -lfreetype: No such file or directory error: linking with `x86_64-pc-linux-musl-gcc` failed: exit status: 1
I'd assume that rust-bin is patched correctly and can generally resolve these dependencies with musl, etc? Given that alacritty is the _same_ in terms of linking for 5 years, the only thing that could affect is that rust-bin/pkg-config can not resolve things properly? Since those deps were always present and that's the only system libraries alacritty directly links to, so all failing at the same time sounds like toolchain issue.
