x86_64-gentoo-linux-musl-gcc -DHAVE_CONFIG_H -I. -D_REENTRANT -D__USE_LARGEFILE64 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Dx86_64 -D SYSLOG -I/usr/include/fuse -D_FILE_OFFSET_BITS=64 -O2 -pipe -march=native -c -o lessfs-lib_qlz15.o test -f lib_qlz15.c || echo ./lib_qlz15.c In file included from lib_qlz15.c:19: lib_safe.h:51:32: error: unknown type name mode_t 51 | int s_open2(const char *, int, mode_t); | ^~~~~~ lib_safe.h:70:26: error: unknown type name mode_t ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl_hardened-20200328-201618 ------------------------------------------------------------------- gcc-config -l: [1] 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.42.0 [2] rust-1.42.0 * Available Java Virtual Machines: (none found) timestamp of HEAD at this tinderbox image: /var/db/repos/gentoo Fri Apr 10 07:38:08 UTC 2020 /var/db/repos/musl Wed Apr 8 18:15:58 UTC 2020 emerge -qpvO sys-fs/lessfs [ebuild N ] sys-fs/lessfs-1.7.0-r1 USE="crypt -berkdb -debug -filelog -lzo -memtrace -snappy"
Created attachment 631856 [details] emerge-info.txt
Created attachment 631858 [details] emerge-history.txt
Created attachment 631860 [details] environment
Created attachment 631862 [details] etc.portage.tbz2
Created attachment 631864 [details] logs.tbz2
Created attachment 631866 [details] sys-fs:lessfs-1.7.0-r1:20200410-084702.log
Created attachment 631868 [details] temp.tbz2
tinderbox_musl has reproduced this issue with version 1.7.0-r2 - Updating summary.