jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-aarch64
<disasm> has anyone tried running hydra on an aarch64 box instead of intel?
<samueldr> any concerns?
<thefloweringash> I run a small hydra on a rock64
<disasm> thefloweringash: thanks! we might give it a try!
<craige> I'd expect the Rpi4 and Odroid devices would be OK too, disasm
andi- has quit [Remote host closed the connection]
andi- has joined #nixos-aarch64
<thefloweringash> The one thing I did was remove the darcs dependency to avoid ghc, which seems a bit spotty on aarch64 still.
<disasm> ah, GHC is primarily what we build :(
<samueldr> disasm: I think the main issue(s) with GHC is output size, and time it takes to build
<samueldr> so it might be relatively doable for someone that knows about ghc to get wrangled
vika_nezrimaya has quit [Ping timeout: 248 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 245 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-aarch64
vcunat has joined #nixos-aarch64
Taneb has joined #nixos-aarch64
<Taneb> I'm considering setting up NixOS on a Raspberry Pi 0 I have lying around. Is there anything written up about how to do this?
<Taneb> ...is this the right channel for that? I've just noticed that it's armv6
<Ashy> Taneb: there's some info here: https://nixos.wiki/wiki/NixOS_on_ARM/Raspberry_Pi
<vcunat> Pi 0 should be 32-bit, but I suppose this channel is still the closest one.
<Taneb> Ashy: vcunat: thanks
vika_nezrimaya has joined #nixos-aarch64
<exarkun> Taneb: pi zero is armv6l? it's going to be a major slog
<Taneb> exarkun: it's not the end of the world for me to either not use NixOS or to go out and get a Pi 3 or 4 (I'm probably in the city where it's easiest to buy a raspberry pi)
<exarkun> armv7l and aarch64 should be a lot easier
<exarkun> there is no up-to-date binary cache for armv6l so you get to build stuff for yourself
<exarkun> which either takes forever for is just impossible due to memory constraints
<exarkun> (unless you have an armv6l build farm hanging out)
jtojnar has quit [Read error: Connection reset by peer]
<exarkun> armv7l is easier to emulate and systems are faster and easier to rent
<exarkun> and there is an official binary cache for aarch64
<Taneb> Well, it will be an adventure :)
jtojnar has joined #nixos-aarch64
<Taneb> Or I go to the raspberry pi shop this weekend
<timokau[m]> Note that (I think) rpi4 is not supported yet
<{^_^}> #63720 (by majewsky, 7 weeks ago, open): Raspberry Pi 4 support
atriq has joined #nixos-aarch64
Taneb has quit [Read error: Connection reset by peer]
atriq is now known as Taneb
ryantrinkle has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
marek has joined #nixos-aarch64
marek has quit [Changing host]
ryantrinkle has quit [Ping timeout: 258 seconds]
jtojnar has quit [Ping timeout: 248 seconds]
ryantrinkle has joined #nixos-aarch64
orivej has quit [Ping timeout: 244 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jtojnar has joined #nixos-aarch64
wildtrees has joined #nixos-aarch64
<t184256> gchristensen: well, this is a fair point
<{^_^}> nix-community/aarch64-build-box#61 (by t184256, 7 weeks ago, closed): add @t184256 as t184256
<t184256> While I can reopen, I don't really have good arguments for trusting me =)
<gchristensen> aye, sorry, I wish there was a easy way to do it anyway
<t184256> So, IDK, meet me at NixCon and make a decision later?
<t184256> I'm going to make a lightning talk on Nix-on-Droid, if that helps.
<gchristensen> col
<gchristensen> cool
<gchristensen> that would be great!
<t184256> Anyway, this is not critical to me, just a nice-to-have
orivej has joined #nixos-aarch64
ris has joined #nixos-aarch64
<DigitalKiwi> what's nix-on-droid
<DigitalKiwi> needs a better website but otherwise looks neat
<DigitalKiwi> does it work on android 6.0?
<DigitalKiwi> t184256: ^
<t184256> DigitalKiwi: if it's aarch64, it should
<t184256> If it's not, then it won't =(
<DigitalKiwi> nexus 5
<t184256> It's just nix executed with proot on Android. Nix is basically a rootfs by itself
<DigitalKiwi> snapdragon 800
<t184256> Sorry, snapdragon 800 is 32 bit
<DigitalKiwi> :<
<t184256> But if somebody builds nix for 32 bit arm the way it is built for aarch64, I can make it work
<t184256> Though, without a binary cache, it will be a pain to build everything
<t184256> I just caved in and bought an aarch64 tablet =/
<samueldr> t184256: note of caution, some aarch64-cpu devices will ship with 32 bit userlands
<samueldr> even still up to this year
<samueldr> I think with android 10 it'll be forced to be aarch64 userlands
<samueldr> one example I know (the only I have personal experience with) is morotola addison / Moto Z Play, which has a Snapdragon 625, but 32 bit userland
<samueldr> I don't know of actual useful source of info for a listing of these terrible devices
<samueldr> only that they exist and it's annoying
<samueldr> I guess for those (once) supported by lineageos you know by their device page
<samueldr> Architecture: arm
<samueldr> CPU: Cortex-A53
<samueldr> compared to a known 64 bit userland
<samueldr> Architecture: arm64
<t184256> Hm
<samueldr> CPU: Cortex-A53
<samueldr> it's an issue with mobile-nixos :)
<t184256> Can one run a statically-linked 64bit binary on such an abomination?
<t184256> I'm not entirely sure how dependent I am on the android userland
<t184256> I don't link to it or anything
<t184256> I'd be grateful if you tried and told me =) If this doesn't inconvenience you much, of course
<samueldr> 99% sure it won't work
<samueldr> the CPU is in a different mode
<samueldr> the kernel too is compiled for 32 bit
<samueldr> I should have said system, and not userland
<samueldr> (I only care about the userland for mobile-nixos)
<samueldr> if it had been 32 bit userland on 64 bit kernel build it would have been less of an issue (for my needs)
<gchristensen> so I'm wondering if more people should be able to merge access requests to the aarch64 builder
<samueldr> what I think will happen is that the easy ones would be merged, and you'd still need to deal with anything else :)
<gchristensen> lol
<samueldr> people will defer to you for the final word
<gchristensen> :(
<gchristensen> bummer b/c it is so safe to make changes :)
<samueldr> I didn't say you shouldn't do it :)
<worldofpeace> ever test that pr samueldr ?
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
v0|d has quit [Remote host closed the connection]
v0|d has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jtojnar has quit [Ping timeout: 258 seconds]
jtojnar has joined #nixos-aarch64