In file included from hxd.h:1, from hxd.c:25: general.h:58:1: error: unknown type name loff_t; did you mean off_t? 58 | loff_t lseek64( int fd, loff_t offset, int whence ); | ^~~~~~ | off_t ------------------------------------------------------------------- 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 05:08:46 +0000 emerge -qpvO dev-util/hxd [ebuild N ] dev-util/hxd-0.70.02-r2
Created attachment 619552 [details] emerge-info.txt
Created attachment 619554 [details] dev-util:hxd-0.70.02-r2:20200315-072757.log
Created attachment 619556 [details] emerge-history.txt
Created attachment 619558 [details] environment
Created attachment 619560 [details] etc.portage.tbz2
Created attachment 619562 [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.
