02:39
ssui-_ss has joined #crux-arm
02:40
ssui-_ss has left #crux-arm [Glined: User has been banned from the network.]
05:32
sajcho has joined #crux-arm
05:33
sajcho has quit [Client Quit]
05:33
sajcho has joined #crux-arm
05:40
sajcho has quit [Quit: Client closed]
07:43
crux-arm-bot has joined #crux-arm
07:43
<
crux-arm-bot >
[ crux-ports-opt-arm64 ]: rust: 1.72.1 -> 1.73.0 (#38)
07:43
crux-arm-bot has left #crux-arm [#crux-arm]
08:28
crux-arm-bot has joined #crux-arm
08:28
crux-arm-bot has left #crux-arm [#crux-arm]
08:28
<
crux-arm-bot >
[ crux-ports-opt-arm64 ]: rust: update .signature
08:52
crux-arm-bot has joined #crux-arm
08:52
<
crux-arm-bot >
[ crux-ports-opt-arm64 ]: go: 1.19.4 -> 1.21.1 (#39)
08:52
crux-arm-bot has left #crux-arm [#crux-arm]
12:36
r0ni has quit [Remote host closed the connection]
12:38
r0ni has joined #crux-arm
15:44
<
beerman >
pitillo go needs a signature bump 🤓
15:57
<
beerman >
actually, wait
16:32
<
pitillo >
I'm on the way... I've got problems downloading go sources
16:32
<
pitillo >
now the rpi3 got frozen I believe... I can't reconnect
16:33
<
pitillo >
let's see if I can plug a monitor and check locally
16:47
crux-arm-bot has joined #crux-arm
16:47
<
crux-arm-bot >
[ crux-ports-opt-arm64 ]: go: update .signature
16:47
crux-arm-bot has left #crux-arm [#crux-arm]
17:01
<
pitillo >
I thought there were a pending PR and it was the signature. I've finally rebooted and updated it
17:02
<
pitillo >
s/were/was
17:31
<
beerman >
there is a new pr for the next go update :D
17:31
<
beerman >
didn't notice there was one more
17:47
<
beerman >
oh, you closed the new pr?
17:48
<
pitillo >
yeah, is that wrong?
17:48
<
pitillo >
only was a .signature update
17:49
<
pitillo >
sorry, I've seen it now
17:49
<
pitillo >
it's an update from 1.21.1 to 1.21.2
17:49
<
beerman >
i deleted the signature to remind you to update it
17:49
<
pitillo >
I see now... reopening
17:50
<
pitillo >
conflict with the signature
17:50
<
beerman >
wait. lets see if i can fix that on my end so it merges
17:58
<
beerman >
woop woop
17:58
crux-arm-bot has joined #crux-arm
17:58
<
crux-arm-bot >
[ crux-ports-opt-arm64 ]: go: 1.21.1 -> 1.21.2 (#40)
17:58
crux-arm-bot has left #crux-arm [#crux-arm]
17:59
<
pitillo >
mesa build problems due to llvm subprojects :(
17:59
<
pitillo >
no way to update llvm on the rpi3, always freeze
17:59
<
pitillo >
nor rust, go....
17:59
<
pitillo >
and I need to modify rust for 32b if I want to use it on the chromebook
18:00
<
pitillo >
I remember I had something prepared on a external disk but I can't find it
18:03
<
pitillo >
got it...
18:11
<
pitillo >
has someone built llvm/go/rust for the rpi3?
18:11
<
beerman >
not me :/ i sold mine
18:31
<
jaeger >
Not recently, I could try if you like but will have to find an rpi3 with crux on it
18:34
<
jaeger >
Or could build it on the M1, alternatively
18:38
<
pitillo >
the M1 is another option...
18:40
<
pitillo >
if you don't mind it would be great jaeger
18:40
<
jaeger >
Which would you prefer?
18:44
<
jaeger >
I guess I should be able to build on the m1 even with rpi3 cflags
18:46
<
pitillo >
I can test those builds from the M1, shouldn't be any problem
18:46
<
pitillo >
faster and less complex for you to look for an rpi3, with crux, and up to date
18:53
<
jaeger >
I'll see if I have a crux uSD card around... most of my rpis have been running 3d printers for a while
19:00
<
jaeger >
Hrmm, looks like it's about time for me to order more uSD cards
19:15
<
jaeger >
Just to make sure I'm on the right page, you want 64-bit packages for llvm, go, and rust, right? Which CFLAGS?
19:26
<
pitillo >
yes, those packages ans optimized CFLAGS please
19:26
<
jaeger >
Same ones as the 3.6 rpi3 release?
19:27
<
pitillo >
order uSD cards, USB sticks and external HD is always an adventure :D
19:27
<
jaeger >
heh, no doubt
19:27
<
pitillo >
yeah, those ones
19:46
<
jaeger >
This install is quite out of date, will take some time to do updates :)
20:42
<
r0ni >
wasi-compiler-rt has bad sig
20:43
<
r0ni >
rust seems to need more than 14gb of free space, my attempts have failed, have to wiat till i can expand hdd again for myself
20:48
<
pitillo >
jaeger: no problem
20:48
<
pitillo >
r0ni: contrib port, not sure if you can contact the maintainer
20:49
<
pitillo >
about the space, I had problems here too on the chromebook where it's hard to expand, I was only able to clean stuff and free some more space. I'll know soon if it keeps dying due to lack of space
20:56
<
r0ni >
i can, it'll just be tomorrow, as i'm about to leave for work atm
20:57
<
r0ni >
trying tos etup rust for another try before i leave lol