x86_64-gentoo-linux-musl-gcc -DHAVE_CONFIG_H -I. -I../include -I../ -O3 -fPIC -I../ -O2 -pipe -march=native -fno-common -falign-functions=32:25:16 -c -o reed_sol_time_gf.o reed_sol_time_gf.c reed_sol_time_gf.c: In function timer_start: reed_sol_time_gf.c:73:21: error: storage size of tv isnt known 73 | struct timeval tv; | ^~ reed_sol_time_gf.c:75:5: warning: implicit declaration of function gettimeofday [-Wimplicit-function-declaration] ------------------------------------------------------------------- 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 13:39:01 +0000 emerge -qpvO dev-libs/jerasure [ebuild N ] dev-libs/jerasure-2.0.0-r1
Created attachment 619834 [details] emerge-info.txt
Created attachment 619836 [details] dev-libs:jerasure-2.0.0-r1:20200315-150258.log
Created attachment 619838 [details] emerge-history.txt
Created attachment 619840 [details] environment
Created attachment 619842 [details] etc.portage.tbz2
Created attachment 619844 [details] logs.tbz2
Created attachment 619846 [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.
tinderbox_musl has reproduced this issue with version 2.0.0-r2 - Updating summary.