02:55 <dlcusa> Farkuhar, you understand me.

11:23 <farkuhar> emmett: What I haven't yet tried, after https://git.crux.nu/farkuhar/pkgutils/commit/f3164d0d4a743880c66953f75e8f6125a62992a7 , is to purge gcc from the system and see whether clang can still compile the pkgutils (now that the gcc extensions will not be available). That's the intended result of yesterday's patch, but I haven't had time to test it properly.

11:30 <farkuhar> And I'm starting to suspect that my firefox build errors (versions 137+) all stemmed from how I built *rust*, not LLVM or clang. I was sent down the wrong path by the error message "unable to find libclang: dynamic loading not supported", which might actually refer to a missing capability in rustc, despite the prominent mention of libclang in the message.

11:33 <farkuhar> The fact that the same error message appeared, both when rust 1.86 was built against the monolithic llvm-project (adapted from KRAK3N), *and* when rust was built against the standalone ports {llvm,clang,lld}, suggests that my dup of the rust port for CRUX-MUSL was missing some critical components.

11:40 <farkuhar> Due to the persistent build failures of firefox 137+, it escaped my attention that some legacy libraries are no longer present in the footprint. Thanks to zorz for pointing out that libipcclientcerts.so is not being built any more.

11:46 <farkuhar> I do have a vague memory of a footprint MISSING error, the one time I pulled out my CRUX-glibc laptop to confirm that firefox 137.0 would build. But after scp'ing the corrected footprint to my main development box, I got distracted by other issues, and the changes were never committed in git.

11:50 <farkuhar> Note to self: create a pre-commit hook that runs `comm -13 <(cut -f3 opt/firefox-bin/.footprint | sort) <(cut -f3 contrib/firefox/.footprint | sort)` , so that spurious entries in the footprint don't get pushed by accident.

12:45 <emmett> farkuhar: thnks for the pkgutils updates. tested on gcc-free system, it does work fine so far

12:47 <emmett> not sure whats the issue causing your firefox build failed

12:47 <emmett> because it build build for me

12:48 <emmett> gonna update firefox from 137.0.1 to 137.0.2 then i will push all the updates on my crux-musl repo

15:42 <farkuhar> emmett: here's the latest build log to illustrate the failures I've been experiencing. https://0x0.st/8OID.2.log

18:18 <farkuhar> I just pushed a bunch of updates to my muslcrux repo, so you can see the current state of the overlay. Anything not in the overlay is built from the official CRUX repos. I'd appreciate any suggestions on the rust port, since that's the most likely culprit for my firefox build failures.

18:22 <SiFuh_> You could add that URL to the channel topic

18:25 <farkuhar> Nah, too lazy to op-up right now. It can wait until CRUX 3.8 is officially released.

19:22 <SiFuh_> Hehe

20:08 <dlcusa> Question: How far back does Per CRUX (pronounced pure) need to be forked from what CRUX has become? The last frinnst release? This is primarily for a Handbook basis.