x86_64-gentoo-linux-musl-gcc -c -I. -Wall -O2 -pipe -march=native -I/usr/include/tirpc -DVERSION=\0.02\ -DXS_VERSION=\0.02\ -fPIC -I/usr/lib/perl5/5.30.1/x86_64-linux/CORE VXI11.c In file included from VXI11.xs:3: /usr/lib/perl5/5.30.1/x86_64-linux/CORE/perl.h:2539:22: error: unknown type name off64_t; did you mean off_t? 2539 | # define Off_t off64_t | ^~~~~~~ /usr/lib/perl5/5.30.1/x86_64-linux/CORE/perl.h:2539:22: note: in definition of macro Off_t ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl_hardened-20200328-201618 ------------------------------------------------------------------- Please see the tracker bug for details. 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-1.42.0 * timestamp of HEAD at this tinderbox image: /var/db/repos/gentoo Tue Mar 31 19:13:24 UTC 2020 /var/db/repos/musl Fri Mar 27 00:25:27 UTC 2020 emerge -qpvO dev-perl/Lab-VXI11 [ebuild N ] dev-perl/Lab-VXI11-0.20.0 USE="(libtirpc)"
Created attachment 628172 [details] emerge-info.txt
Created attachment 628174 [details] dev-perl:Lab-VXI11-0.20.0:20200331-211501.log
Created attachment 628176 [details] emerge-history.txt
Created attachment 628178 [details] environment
Created attachment 628180 [details] etc.portage.tbz2
Created attachment 628182 [details] temp.tbz2
Interestingly, musl does define (conditionally) off64_t in dirent.h
tinderbox_musl has reproduced this issue with version 0.30.0 - Updating summary.
This is somewhat of a Perl bug (since the missing include is in a Perl header)...
Toralf / Ago: what I'd need is the build log of dev-lang/perl in such a container... any chance?
(In reply to Andreas K. Hüttel from comment #10) > Toralf / Ago: what I'd need is the build log of dev-lang/perl in such a > container... any chance? not for this container - that image is gone. Currently I tried to reproduce it but at a current musl image dev-perl/Lab-VXI11-0.30.0 works (un)fortunately. I tend to close this as long as it cannot be reproduced.
(In reply to Toralf Förster from comment #11) > (In reply to Andreas K. Hüttel from comment #10) > > Toralf / Ago: what I'd need is the build log of dev-lang/perl in such a > > container... any chance? > > not for this container - that image is gone. > > Currently I tried to reproduce it but at a current musl image > dev-perl/Lab-VXI11-0.30.0 works (un)fortunately. > > I tend to close this as long as it cannot be reproduced. WFM
appeared recently at the tinderbox image 17.0_musl-j4-20220628-041652
Created attachment 788393 [details] emerge-info.txt
Created attachment 788396 [details] dev-perl:Lab-VXI11-0.30.0:20220628-115427.log
Created attachment 788399 [details] emerge-history.txt
Created attachment 788402 [details] environment
Created attachment 788405 [details] etc.portage.tar.bz2
Created attachment 788408 [details] temp.tar.bz2
This is actually a problem in the upstream module build system. I'll prepare a fix and get it committed.