<pitillo>
tomorrow morning I'll throw another st1 build on that st0 and I'll review mistmatches (hope the eudev stuff will be fixed)
<jaeger>
sounds good
guido_rokepo has joined #crux-arm
beerman has quit [Quit: Bridge terminating on SIGTERM]
beerman has joined #crux-arm
<pitillo>
after this morning last changes the M1 finished stage1 build with only one error downloading rsync
<pitillo>
sepen has applied these changes and added some more (device optimization on device tree for example) in the crux-arm-release repo
<pitillo>
this is starting to smell awesome
<jaeger>
nice
<jaeger>
Also, another handy thing you can do with docker to persist data between container runs is use mounted volumes
<jaeger>
Something like 'v $(pwd):/data' to mount the current directory as /data in the container
<pitillo>
yeah, I was thinking in mounting a nfs based volume... but as far as I have lot of space locally and probably "harder logic", discarted that nfs thing and started thinking about a local development dir... but I still need more reading time and knowledge (I use volumes on my firsts tests with my personal web running nginx)
<pitillo>
lol
<pitillo>
sepen just implemented the exit on the Makefile \o/
<pitillo>
for both stages... stage0 too.... may be not needed but for a bootstrap is important too... interesting
<pitillo>
jaeger: just out of curiosity and if it's possible to know, how many time are you using docker? do you use it on a personal level or on a professional level as well?
<jaeger>
I use it a LOT both for work and personal
<jaeger>
I do all of my port update build tests in containers in my home lab, for example
<jaeger>
pitillo: for crux-arm-release should the main or 3.7 branch be used? I see recent changes in both
<jaeger>
Looks like the 3.7 branch has the exit added
guido_rokepo has quit [Quit: guido_rokepo]
<jaeger>
Oh, another question - if both 32-bit and 64-bit releases are desired for rpi3 and rpi4, which should be named 'raspberrypiX.mk' and should the other one be 'raspberrypiX-32.mk' or -64 or something else?
<pitillo>
good point, but if no one will maintain 32b work for the rpiX, no need to mess with that. I'm personally focused on 64b on any 64b capable device
<pitillo>
if there is someone interrsted inthe 32b release for anybrpiX, I'll vote to add the 32b suffix for them and maintain the name without suffix for 64b
<pitillo>
interesting your maintenance work with docker. I can tell you've been using it for a long time
<jaeger>
Works for me, thanks
<jaeger>
Yes, lots of use. I admit I don't use nearly all its features and I'm not an expert but I use it quite often for my simple tasks :)
<pitillo>
jaeger: always 3.7... if I understood it right, we can merge into main any interesting job done (I'd say, for long term support)
<jaeger>
OK, cool. Makes sense
<pitillo>
not an expert but you have lot of knowledge and experience, that's cool
<jaeger>
I should have a 3.7 branch ready for the raspberrypi4-arm64 overlay repo today
<pitillo>
niiiice
<pitillo>
I'm waiting at the office for people to leave just to poweron the laptop to start updating locally and testing
<jaeger>
:D
<pitillo>
I'd like to prepare the first generic RC for a arm64
<pitillo>
s/a arm64/arm64
<pitillo>
we were speaking this morning about how we can handle all the work done in different steps/stages to provide a way to improve optimizations and make them easy to build
<pitillo>
I miss CRUX meetings xD
<pitillo>
and of course, something I could never do, CRUX con
<jaeger>
Those were pretty fun
<jaeger>
There's a typo in core-arm64/libgmp
<jaeger>
cd gmp-$version}
<pitillo>
arf|@#@~|
<pitillo>
thanks, I'll fix
<pitillo>
done
<pitillo>
sometimes I hate to work from the laptop instead of my main machine
<pitillo>
segfault trying to download rsync source... the only one with download problems... and segfaulting
<jaeger>
I will test it
<jaeger>
no, no problem downloading rsync (using curl)
<pitillo>
interesting
<pitillo>
just trying to figure out why pkgmk -do is giving that segfault, only with that download
<jaeger>
does the download command work manually?
<pitillo>
it did for all the other ports, it was just rsync
<pitillo>
I'm rebuilding again from a clean and fresh copy with all the lasts change done
<pitillo>
do you know if it's possible to check temp from command line on M1 silicon (from what I've read I've only found some GUI apps, but nothing to check from command line)
<jaeger>
No idea, sorry
<pitillo>
thanks anyways
<pitillo>
rsync source moved after last update (all sources are in /src instead of root where we are looking for sources)