|Run-time dependency gobject-2.0 found: YES 2.62.5 subprojects/libinsane-gobject/src/meson.build:46:0: ERROR: Program(s) [g-ir-scanner] not found or not executable A full log can be found at /var/tmp/portage/media-libs/libinsane-1.0.3/work/libinsane-1.0.3-build/meson-logs/meson-log.txt * ERROR: media-libs/libinsane-1.0.3::gentoo failed (configure phase): ------------------------------------------------------------------- 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.8 [2] python3.7 [3] python3.6 [4] python2.7 (fallback) repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Thu, 12 Mar 2020 21:38:56 +0000 emerge -qpvO media-libs/libinsane [ebuild N ] media-libs/libinsane-1.0.3 USE="-doc -gtk-doc -test"
Created attachment 618270 [details] emerge-info.txt
Created attachment 618272 [details] emerge-history.txt
Created attachment 618274 [details] environment
Created attachment 618276 [details] etc.portage.tbz2
Created attachment 618278 [details] logs.tbz2
Created attachment 618280 [details] media-libs:libinsane-1.0.3:20200312-233256.log
Created attachment 618282 [details] temp.tbz2
The first attempt to tinderbox a musl image failed at all. I'll mass close therefore all filed bug reports of the last days related to this tinderbox image. Please feel free to re-open if you think that the bug is real in musl and not fixed by the musl overlay.
