Created attachment 873180 [details] build.log Missing type definition of off64_t causes build failure. Based on https://stackoverflow.com/a/34853360, this seems to be something that could be worked around with: ``` CFLAGS="${CFLAGS} -Doff64_t=__off64_t" ``` However, I made a Portage env for this and assigned the ebuild to target that env, and the CFLAGS weren't picked up. I presume this means Perl ebuilds forcibly override these, because I otherwise see nothing in the ebuild overriding or limiting CFLAGS. That, or I just failed to create a Portage env correctly... I also tried building this in my gcc-lto env, which also seems to have failed to do anything: I still see `clang` being called in the trace. My best guess is that this is a missing otherwise-assumed header include that could be patched (and probably upstreamed); Perl stuff is out of my wheelhouse so I'll recuse myself from writing such a patch for now I think.
Created attachment 873181 [details] emerge --info
Created attachment 873182 [details] emerge -pqv
Looks like it can't find dev-libs/expat rather than a LFS64 shim issue in musl. I see your gentoo repo was last updated on the 09/10/23 so could you try the following: 1. emerge --sync 2. check it successfully updated 3. emerge -va1 dev-libs/expat 4. emerge -va1 dev-perl/XML-Parser If this fails try: perl-cleaner --all Then repeat the above steps. This should clear it.
The sync date thing is weird - this rootfs didn't exist on Sept 10, and I know I ran an eix-sync some time last week at the latest. Anyway though... - ran steps 1-4, did not fix (same build error) - ran perl-cleaner --all ("no package needs to be reinstalled"), re-ran steps 3&4... no dice. same build error as in OP.
Thanks for testing. If you could upload the new emerge --info just to help with confirming that would be great.
Created attachment 873184 [details] new emerge --info
You didn't include how you deduced the type error issue, as it's not in the log. Anyway, it's probably really bug 911233.
Ah sorry, indeed the build.log doesn't represent what I see on my screen, which is a bunch of Expat-related compile errors about the missing type. I wonder which log those are in, and why they aren't in the pasted (I had blindly assumed the log file was the same as what was in my console). Rebuilding dev-lang/perl now, we'll see if this helps.
Confirming that a oneshot rebuild of dev-lang/perl fixed the issue, and now dev-perl/XML-Parser builds fine (and quite quickly!)
