libtool: compile: x86_64-gentoo-linux-musl-gcc -DHAVE_CONFIG_H -I. -O2 -pipe -march=native -fno-common -falign-functions=32:25:16 -c scanroutines.c -fPIC -DPIC -o .libs/scanroutines.o scanroutines.c: In function scan_routine_BYTEARRAY_EQUALTO: scanroutines.c:372:5: error: unknown type name uint; did you mean int? 372 | uint length = user_value->flags; | ^~~~ | int ------------------------------------------------------------------- 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 <== Sun, 15 Mar 2020 17:38:35 +0000 emerge -qpvO dev-util/scanmem [ebuild N ] dev-util/scanmem-0.17 USE="-gui -static-libs" PYTHON_SINGLE_TARGET="python3_6 -python3_7"
Created attachment 619960 [details] emerge-info.txt
Created attachment 619962 [details] dev-util:scanmem-0.17:20200315-183109.log
Created attachment 619964 [details] emerge-history.txt
Created attachment 619966 [details] environment
Created attachment 619968 [details] etc.portage.tbz2
Created attachment 619970 [details] logs.tbz2
Created attachment 619972 [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.
