cd /var/tmp/portage/dev-libs/xerces-c-3.2.2-r1/work/xerces-c-3.2.2_build/src && gencat /var/tmp/portage/dev-libs/xerces-c-3.2.2-r1/work/xerces-c-3.2.2_build/src/XercesMessages_en_US.cat /var/tmp/portage/dev-libs/xerces-c-3.2.2-r1/work/xerces-c-3.2.2/src/xercesc/util/MsgLoaders/MsgCatalog/XercesMessages_en_US.Msg /bin/sh: gencat: command not found ninja: build stopped: subcommand failed. * ERROR: dev-libs/xerces-c-3.2.2-r1::gentoo failed (compile phase): * ninja -v -j1 -l0 failed * ------------------------------------------------------------------- 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 dev-libs/xerces-c [ebuild N ] dev-libs/xerces-c-3.2.2-r1 USE="iconv -curl -doc -examples -icu -static-libs -test -threads" CPU_FLAGS_X86="sse2"
Created attachment 620292 [details] emerge-info.txt
Created attachment 620294 [details] dev-libs:xerces-c-3.2.2-r1:20200316-032123.log.bz2
Created attachment 620296 [details] emerge-history.txt
Created attachment 620298 [details] environment
Created attachment 620300 [details] etc.portage.tbz2
Created attachment 620302 [details] logs.tbz2
Created attachment 620304 [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.