00:34 <farkuhar> jaeger: US/Eastern

00:35 <jaeger> Hrmm, do you commit on a system set to UTC?

00:35 <jaeger> Curious because gitea was giving timestamps ending in Z shorthand for your commits

00:36 <farkuhar> Yes, my latest commits are on a system set to UTC.

00:38 <jaeger> ok

00:39 <jaeger> thanks, just verifying what I was seeing

09:49 <beerman> i am currently checking if there is some other problem.. the current rust version in opt does not build either inside a container and also outside of containers. I have no idea when it broke, because i was rebuilding it constantly to prepare my rust-wasm port and possibly a rust-mingw port.. so thats unexpected^10

09:55 <beerman> on a host that didn't update to llvm 17.0.5 yet it seems to succeed

10:17 <beerman> judging by my container: its not llvm 17.0.5..

12:50 <farkuhar> these rust builds are failing in both CRUX 3.7 and 3.8 containers?

12:53 <beerman> 3.8 works fine for me

12:55 <beerman> i also have one successful build of rust 1.74.0 on 3.7 out of 5 places I tried by now

12:57 <farkuhar> yesterday you suspected that a newer version of binutils might be the fix. Any attempt to follow up on that idea?

13:00 <beerman> not yet, no

13:01 <beerman> that was the easiest suggestion after it worked for the 3.8 container, but now that I built it on one 3.7 install I wouldn't make the same assumption again

13:02 <beerman> Not sure whats to blame yet really. the host that managed to build it has a few ports out of date, like cmake and libxml2, but downgrading these doesn't unclog it for anything else, so... it appears not to be these easy guesses either :D

20:49 <beerman> ok, I know whats up. At least partly. sccache is to blame, but I have no idea why :)

20:51 <farkuhar> it makes sense, since I'm getting a successful build on an up-to-date CRUX 3.7 with no sccache.

22:59 <jaeger> These funky rare issues are why I stopped using any of the distcc/ccache stuff, sadly

22:59 <jaeger> rare but enough to be annoying