01:10 <r0ni> arm64 pkg repo up to date incl firefox 119, i'll do pine64 later, which has more pkgs overall... but i still haven't decided to keep or not one or the other... maybe just keep both anyway see how long i maintain my sanity

01:10 <r0ni> tho that is questionable

06:22 <pitillo> xD

06:22 <beerman> Welcome to the CRUX maintainers experience

06:22 <beerman> ☕

10:08 <r0ni> i'm thankful for this M1 to build on, I don't think I'd go this far actually on my pbp lol

10:09 <r0ni> just need to find a way to completely cut out sleeping

10:47 <pitillo> sleeping is a must... don't cut it out xD

14:18 <pitillo> /mnt/pkgmk/work/rust/src/rustc-1.72.1-src/build/armv7-unknown-linux-gnueabihf/stage1/lib/librustc_driver-2526ec18591b43cb.so(+0x5ec688)[0xb3ccc688]

14:19 <pitillo> /lib/libc.so.6(__default_sa_restorer+0x0)[0xb33babe0]

14:19 <pitillo> rustc exited with signal: 11 (SIGSEGV)

14:19 <pitillo> error: could not compile `rustc_hir_typeck` (lib)

14:19 <pitillo> after 12 days building rust...... :_(

14:19 <jaeger> :(

15:12 <beerman> 1.72.1 woot

15:12 <beerman> and 12 days, damn

15:12 <beerman> rip

15:55 <pitillo> who told 12 days? 8)

15:55 <pitillo> warning: build failed, waiting for other jobs to finish...

15:55 <pitillo> Build completed unsuccessfully in 21 days, 6:43:57

15:56 <pitillo> I don't understand anything....

15:56 <pitillo> but yeah, it was 21 days, not 12.... xD

16:01 <jaeger> oof

16:01 <jaeger> Time to build on the m1 instead?

16:04 <ukky> We might re-evaluate the need for cross-compiling. Native build is better, of course, but if full system rebuild cannot complete in 24 hours, then other options should be considered.

16:09 <pitillo> jaeger: this is 32b. I'm not sure if I can build a 32b enviroment on the m1.... it should be possible, but not sure

16:09 <pitillo> ukky: patience and coffee isn't a solution.... at least for the chromebook xD

16:10 <jaeger> I haven't tried to build 32b on it, not sure

16:10 <pitillo> what would habppen with the jornada 720? a year to build rust if it could be possible....

16:10 <beerman> 🫠

16:12 <ukky> it is probably okay to wait a few days for a build to complete, but only if you know the build will be successful.

16:13 <pitillo> ukky: yeah, I know.... but the development process has these inconveniences...

16:13 <pitillo> long time ago with old devices, firefox and chromium were a pain... it didn't take 21 days, but for sure 3-4 days to get the error, research and give them another try

16:14 <pitillo> I was curious about the chromebook... I will try to go ahead without rust btw

16:14 <beerman> By the time your build finished you have two new releases

16:20 <ukky> At work, the whole rootFS for the embedded product I am working on (aarch64) takes about 6-8 hours to complete, including building chromium. Without chromium it takes 3-4 hours. x86 system is used to build aarch64 rootFS.

16:50 <pitillo> for that scenario I'd prefer to use a native build, more now with lot of strong/fast alternatives. M1 is the example but there are overthere very good ones too. Cross is always there and it's another solution