<r0ni_>
hey there they are! heh, there's likely more footprint fixes yet, but I haven't had more time to try building things
<pitillo>
r0ni_: don't worry! there is no need to rush
<r0ni_>
trying to make it so I can try to install a meta-port for one of the DEs I maintain and there's no failures along the way (easier said than done) ;)
<pitillo>
thanks for all those PR to get all synced and fixed!!!!
<pitillo>
yeah, sounds easier that it really is, but like always, bit by bit, there is no need to rush
<pitillo>
officially CRUX-ARM 3.8 isn't announced yet xD
<r0ni_>
perfect! I still need to work out rpi5 changes as well soon
r0ni_ is now known as r0ni
<pitillo>
there is an optimized rpi5 release build and uploaded :D
<r0ni>
oh i didn't notice a rpi5 rootfs was there heh
<pitillo>
there are aarch64 releases ready....
<r0ni>
was going to change to kernel 6.12 branch like x86 is
<pitillo>
I'm currently using the odroidxu4 and the crux-rootfs repo to prepare armhf builds (currently building the generic... but it takes time... I wasn't able to use the Mac M4 to create armhf containers, neither podman or docker)
<r0ni>
oh yeah apple seems to limit things to just arm64, no support for armhf and others
<pitillo>
interesting, it's currently a 6.6.63 so it could be interesting to keep it synced
<r0ni>
it builds, i've got it locally i just haven't upated the repo in some time
<pitillo>
r0ni: I've made some tests and I can run a armhf container on docker (podman doesn't support it right) but there are weirdness inside... prt-get for example doesn't work as expected
<pitillo>
it's just curious.....
<pitillo>
r0ni: good to know. I haven't a device but it'd cool to have it built and tested...
<r0ni>
any other systems run? like debian or anything?
<pitillo>
I'm planning to get a micro SD card to do a full test of old devices with current 3.8 release and try to improve documentation at web
<pitillo>
it's currently a bit sheet for many devices....
<pitillo>
r0ni: I haven't tested that...
<r0ni>
i think all my old 32bit rpi devices no longer work... i can't even pull them out for testing, they all broken except for maybe a rpi2
<pitillo>
it could be a good test to check if our toolchain (real hard float) makes it break vs the multilib toolchain used by Debian
<pitillo>
how they broke?!?!?!
<pitillo>
I still have the rpi1 on its case in a box xD
<r0ni>
a few zero devices, all just no longer power on, i never figured out what went wrong
<r0ni>
or maybe they were and i just didn't refresh the page
<pitillo>
r0ni: yeah, yesterday we were cooking them :D
<r0ni>
pitillo: ok good, was testing my sanity a moment there ;)
<pitillo>
xDDD
<pitillo>
we are on the way....
<pitillo>
may be no one noticed that there are some changes at the webpage...
<r0ni>
oh i see, updated downloads!
dlcusa has quit [Remote host closed the connection]
crux-arm-bot has joined #crux-arm
<crux-arm-bot>
[ opt-arm64/3.8 ]: go: update to 1.24.2
crux-arm-bot has left #crux-arm [#crux-arm]
<jaeger>
I'm still using my old rpi2 as an NTP server with a GPS module :D
<jaeger>
old but solid
<pitillo>
nice one
<pitillo>
well... another goal here while building armhf releases on the odroidxu4.... I'm building a multilib gcc on the orangepiPC... let's see what I can break now....
crux-arm-bot has joined #crux-arm
<crux-arm-bot>
[ opt-arm64/3.8 ]: go: fix release
crux-arm-bot has left #crux-arm [#crux-arm]
CrashTestDummy has joined #crux-arm
CrashTestDummy has quit [Read error: Connection reset by peer]