need-builtin= \ need-modorder=1 make[3]: *** No rule to make target /var/tmp/portage/net-misc/dahdi-3.1.0-r1/work/dahdi-linux-3.1.0/drivers/dahdi/ap400/ap400_drv.o, needed by /var/tmp/portage/net-misc/dahdi-3.1.0-r1/work/dahdi-linux-3.1.0/drivers/dahdi/ap400/ap400.o. Stop. make[2]: *** [scripts/Makefile.build:503: /var/tmp/portage/net-misc/dahdi-3.1.0-r1/work/dahdi-linux-3.1.0/drivers/dahdi/ap400] Error 2 make[1]: *** [Makefile:1693: /var/tmp/portage/net-misc/dahdi-3.1.0-r1/work/dahdi-linux-3.1.0/drivers/dahdi] Error 2 make[1]: Leaving directory /usr/src/linux-5.5.9-gentoo ------------------------------------------------------------------- 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 * [2] x86_64-gentoo-linux-musl-9.3.0 clang version 10.0.0 Target: x86_64-gentoo-linux-musl Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.0 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.7 [3] python3.6 [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-bin-1.41.1 [2] rust-1.41.1 * The following VMs are available for generation-2: repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Mon, 16 Mar 2020 02:38:31 +0000 emerge -qpvO net-misc/dahdi [ebuild N ] net-misc/dahdi-3.1.0-r1 USE="-flash -oslec"
Created attachment 620306 [details] emerge-info.txt
Created attachment 620308 [details] emerge-history.txt
Created attachment 620310 [details] environment
Created attachment 620312 [details] etc.portage.tbz2
Created attachment 620314 [details] net-misc:dahdi-3.1.0-r1:20200316-035123.log
Created attachment 620316 [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.