jaeger changed the topic of #crux-arm to: CRUX-ARM 3.7 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-7 | Logs: https://libera.irclog.whitequark.org/crux-arm/
<jaeger> ok, got the rpi5 up with a generic rootfs, starting optimized builds
<jaeger> I have to say it's nice to have 8GB RAM on a pi
<pitillo> 8Gb RAM should be amazing on any ARM device. Most builds can be done there, just the bigger ones will give problems so that's a step ahead
sajcho has joined #crux-arm
<sajcho> I can confirm. I build everything in tmpfs. Outside of gcc, rust, firefox...
<sajcho> By the way. I left xorg. I'm only working on wayland at the moment.
sajcho has quit [Quit: Client closed]
<pitillo> nice
<r0ni> pitillo: it fails trying to do something with attr, generally if i see a failure, i reboot and try again though, one can't do a make bootstrap again if stage0 (or 1) has completed, so I start deleting folders and re-un it until it works
<r0ni> it leaves me witha symlinked rootfs in the end, so i have to assume all steps have finished
dim_ has joined #crux-arm
dim44 has quit [Ping timeout: 276 seconds]
<pitillo> r0ni: but it didn't?
<pitillo> instead of dwlering, try to touch objectives. Prpbably they can't be used because they were built time ago
<pitillo> s/dwlerin/deleting
<jaeger> Man, the rpi5 feels quite fast. I should time some of the large package builds after the rootfs work
<beerman> Sounds very promising :)
<pitillo> yeah, good feelings from both
<jaeger> question, why is docker in opt-arm64? vs. contrib
<jaeger> Maybe it needed an overlay in the past
<jaeger> pitillo: can you or sepen create a crux-ports-raspberrypi5-arm64 repo?
<jaeger> I'll be happy to push to it but I don't think I can create it