jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
emmett1 has joined #crux-devel
<jaeger> rust 1.75.0 doesn't build for me in a clean container: https://crux.ninja/tmp/rust.log.txt
groovy2shoes has quit [Ping timeout: 268 seconds]
groovy2shoes has joined #crux-devel
emmett1 has quit [Ping timeout: 240 seconds]
<beerman> jaeger interesting!
<beerman> i only built it two times yesterday, and it also built like that on the raspberry pi. I'll update a few more machines and see if I can shake that out of the tree
<beerman> container or not, on 6 different machines it built fine. I can change the config.toml from changelog-seen to change-id but this is just an indicator and does nothing for the build itself
<beerman> the fact that it says file not found would make me want to check the disk space, but I assume thats no problem eh?
<beerman> fwiw, this is my build log in my container https://sprunge.us/xVV2eD
SiFuh has quit [Remote host closed the connection]
SiFuh has joined #crux-devel
jue has joined #crux-devel
<jue> wrt rust: my first try to build fails as well, got it fixed by removing the old version first
<beerman> hu, didn't have the same problem on my non container deployments.. color me surprised
<ivandi> rust still fails for me, even after removing the old package
<ivandi> it fails at bootstrap first: https://github.com/rust-lang/rust/issues/117885
<ivandi> after creating $CARGO_HOME/registry/src the bootstrap passes but stage0 fails with error: --remap-path-prefix must contain '=' between FROM and TO
ivandi has quit [Quit: WeeChat 4.1.2]
ivandi has joined #crux-devel
ivandi has quit [Quit: WeeChat 4.1.2]
ivandi has joined #crux-devel
ivandi has quit [Client Quit]
ivandi has joined #crux-devel
<ivandi> remap-debuginfo = false in config.toml fixes the build
ivandi has quit [Quit: WeeChat 4.1.2]
ivandi has joined #crux-devel
<beerman> deleting $CARGO_HOME/registry/src shows the fault for me, and remap-debuginfo = false sure fixes it for me
<beerman> I'll push that soon and try to not forget it to reenable it later
<jaeger> It seems to fix the build here, too