ryantrinkle has quit [Ping timeout: 258 seconds]
prusnak has quit [Quit: Connection closed for inactivity]
ToxicFrog has quit [Quit: WeeChat 2.6]
ToxicFrog has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
vika_nezrimaya has quit [Ping timeout: 260 seconds]
lovesegfault has joined #nixos-aarch64
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
lovesegfault has quit [Quit: WeeChat 2.7]
orivej has quit [Ping timeout: 260 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zarel_ has quit [Ping timeout: 260 seconds]
<thefloweringash> My rock64 on 19.09.1625.0dc46b0e1c8 seems to be unable to build a kernel due to "internal compiler error: Segmentation fault", seemingly at random. Does this ring any bells for anyone?
<thefloweringash> lopsided98: I didn't know pkgsCross.sheevaplug existed. I still have my sheevaplug. Does it build enough to boot a nixos?
Thra11 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<lopsided98> thefloweringash: I don't have a sheevaplug, I just used that package set to get an armv5tel cross-compiler. I used it to build ArduPilot for a Parrot quadcopter running an ancient kernel and userspace.
zupo has joined #nixos-aarch64
vika_nezrimaya has joined #nixos-aarch64
pbb has joined #nixos-aarch64
<THFKA4> thefloweringash: that sounds like you're running out of RAM, reduce your number of threads
<vika_nezrimaya> Looks like k3s runs well on NixOS on Rasbperry Pi (at least it seems to launch?)
<vika_nezrimaya> Except it's not packaged... :c
vika_nezrimaya has quit [Remote host closed the connection]
vika_nezrimaya has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 265 seconds]
zarel has joined #nixos-aarch64
Thra11 has quit [Quit: WeeChat 2.6]
zupo_ has quit [Ping timeout: 258 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Thra11 has joined #nixos-aarch64
<samueldr> thefloweringash: other alternative could be instruction set mismatch, e.g. build on an Cortex-A96 with stuff that's not on whatever cortex you run on
<samueldr> which is something that's been a known but overlooked and underdocumented purity issue
<samueldr> (though, maybe not a thing anymore since the change with -march flags?)
<{^_^}> #56285 (by cleverca22, 43 weeks ago, open): python ctypes extension fails to build due to purity issues
<samueldr> btw also something that is in practive an issue in x86-land
<samueldr> >> building an armv7l-linux python on an aarch64-linux kernel
<samueldr> this is not the same, here I'm thinking both aarch64-linux, but different cpu feature sets :)
<samueldr> (well, maybe the fix is the same though)
lovesegfault has joined #nixos-aarch64
<clever> samueldr: yeah, if your mixing arm64 cpu's, it will sucessfull build libffi on one, but then fail to use it on another