dongcarl has quit [Ping timeout: 256 seconds]
rajivr has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
patagonicus3 has joined #nixos-aarch64
patagonicus has quit [Ping timeout: 246 seconds]
patagonicus3 is now known as patagonicus
alp has quit [Ping timeout: 272 seconds]
andi- has quit [Remote host closed the connection]
andi- has joined #nixos-aarch64
LnL has quit [Ping timeout: 272 seconds]
LnL has joined #nixos-aarch64
LnL is now known as Guest15009
dongcarl has joined #nixos-aarch64
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 264 seconds]
cole-h has quit [Quit: Goodbye]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<patagonicus> Hmm. I've just realized that I'll need the individual files anyway since I want the systems to use them as their config for nixos-rebuild once they're deployed (basically I want to share the config so I can keep the one for rebuilding on the system the same as when I redeploy them).
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<patagonicus> http-parser doesn't build due to a bug that has been fixed upstream, but isn't included in any release yet. Should I "backport" the patch for fixing this in nixpkgs or just wait for the next release? (The "backport" is just git format-patch of one commit and adding this as a patch to the nix package).
Guest15009 has quit [Quit: exit 1]
LnL has joined #nixos-aarch64
LnL is now known as Guest37915
Guest37915 has quit [Changing host]
Guest37915 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
Guest37915 is now known as LnL
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
julm has quit [Remote host closed the connection]
knerten has joined #nixos-aarch64
julm has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Read error: Connection reset by peer]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
<patagonicus> I just added a wiki page for the HC1&HC2: https://nixos.wiki/wiki/NixOS_on_ARM/ODROID-HC1 would be great if someone could take a look at it since it's my first edit on the NixOS wiki. :)
<patagonicus> Next up is cross compiling instructions for the general Nix on ARM page.
orivej has joined #nixos-aarch64
<makefu> patagonicus: good first article, thanks for your contribution! patagonicus++
<{^_^}> patagonicus's karma got increased to 5
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
<patagonicus> :)
alp has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
alp has quit [Ping timeout: 256 seconds]
orivej has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
bennofs[m] has left #nixos-aarch64 ["Kicked by @appservice-irc:matrix.org : Idle for 30+ days"]
goibhniu has quit [Quit: Idle for 30+ days]
alp has joined #nixos-aarch64
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
alp has quit [Ping timeout: 260 seconds]
alp has joined #nixos-aarch64
orivej has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
orivej_ has quit [Ping timeout: 258 seconds]
cole-h has joined #nixos-aarch64
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
<patagonicus> Meh. Crosscompiling the armv7l-multiplatform image fails because "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." for btrfs-progs.
orivej has quit [Read error: Connection reset by peer]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Read error: Connection reset by peer]
orivej_ has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
alp has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
rajivr has quit [Quit: Connection closed for inactivity]
alp has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej_ has joined #nixos-aarch64
<Ke> appears wrong?
<patagonicus> Yeah, I don't know. I'm going back to the known good commit of nixpkgs I have and will try around a bit. Maybe I'll see if I can get something like bash built and then I can see if it builds at head and bisect if necessary.
<Ke> I haven't been looking into this yet, but don't you get normal packages from caches?
<patagonicus> armv7l doesn't have an official cache. And cross compiling changes hashes, so the cache is different from natively compiled packages as well.
<Ke> yes, thought as much
<Ke> was going to ask about it at some point
<patagonicus> A bit annoying, because if you cross-compile an installer image, then the first nixos-rebuild will recompile everything from scratch. :D
orivej_ has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
<samueldr> yes, but at the very least, it is understandable why so :)
alp has quit [Ping timeout: 260 seconds]
<patagonicus> Yep. Not complaining too much, it makes sense. And it probably wouldn't take that long, once I get my extra HC2s (I think the ETA is Monday).
<patagonicus> So, very surprisingly: if you use the workarounds for the things that are known to be broken for cross compiling it actually works.
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
<samueldr> you don't say!
cole-h has quit [Quit: Goodbye]
orivej has quit [Read error: Connection reset by peer]
orivej_ has joined #nixos-aarch64
orivej_ has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Read error: Connection reset by peer]
orivej_ has quit [Read error: Connection reset by peer]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 258 seconds]
orivej_ has joined #nixos-aarch64
<Jake[m]> samueldr: is the pinebook pro stuff being built and cached anywhere like on hydra? If not, is there a way to make that happen? I'd be happy to do what need to be done there.
<samueldr> no, not being built and cached
<samueldr> a policy decision would need to be made about building non-mainline artifacts for misc. machines
orivej_ has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
<noneucat> hello all!
<noneucat> out of curiosity, what kind of hardware are people using for native aarch64 builds? i'm currently looking at getting one of pine64's rockpro64 boards to use as a build box but i'm wondering what people are using here
<Ultrasauce> jetson tx2
<samueldr> many users are using rockpro64s
<samueldr> I personally am using an ROC-RK3399-PC, but I wouldn't recommend it more than any other good RK3399 board
<samueldr> (oh, and hi! 👋)
<samueldr> easy to acquire, easy to get NixOS going, and fast, not sure there is much better than RK3399 boards right now
<samueldr> tip: multi-line matrix messages get massaged into an opaque link on IRC https://stuff.samueldr.com/screenshots/2020/07/20200718171704_5iwgsk19ufdgx2tfl1y.png
<noneucat> that is unfortunate :( noted for the future
<samueldr> some users also "rent" "big boy" ARM servers as needed from packet.net https://www.packet.com/cloud/servers/c2-large-arm/
<samueldr> "big boy" being their own term :)
<samueldr> there is the community build box that exists too, read its README https://github.com/nix-community/aarch64-build-box
<samueldr> I wouldn't use the community box for anything that ends up on machines I want to trust
<samueldr> (well, on their storage, e.g. I'm fine putting an SD card built on it on a raspberry pi and then erasing and putting something trustable on the same pi)
<samueldr> I should maybe try and make a pi4 build the same thing I would for the rk3399 board and see how close their perfs are, but first I'd need to have a non-SD storage solution for both
<samueldr> (well, my rk3399 board uses a usb drive, but still cheapy flash based which harms perfs)
<noneucat> i did look into the community box + hosted servers but i think i'd just prefer a local box to hack on haha
<noneucat> for various reasons
<samueldr> the community box is helpful in getting the thing built when it fails in long~ish builds
<samueldr> but I do understand the feeling of keeping builds home
<noneucat> understood 👍️
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
<samueldr> noneucat: I have the build currently building more than previously using https://gist.github.com/c5dff3966dded5cb842e22e1d4dadaeb
<samueldr> I'll let you know if it ends up a success or not
<samueldr> I'm surprised taking the diff of only one file doesn't end up with breakage everywhere
<noneucat> good news! looking forward to it 👌
<samueldr> might be easier than building on top of the binutils upgrade pr
<noneucat> yeah
<noneucat> if it works out it would be easier
orivej has quit [Ping timeout: 256 seconds]
<samueldr> thanks for looking into it and figuring that out
<noneucat> no problem! :)
<Jake[m]> i've been renting ec2 servers, like a1.2xlarge which cost around 10 cents an hour. Does anyone have an idea of how much faster those are than an rk3399?
<samueldr> sorry I don't, but expect possibly enough faster, especially if their storage is fast
<noneucat> i'm curious to see how the new apple silicon machines will perform compared to existing hardware
<samueldr> compared to server hardware, probably nothing to write home about unless they start *also* optimizing for heavy workloads early on
<samueldr> for desktop~ish hardware, look at ipad pro cpu benchmarks and compare
<samueldr> now assume that the DTK is going to be underspecced compared to an equivalent mac mini silly
<samueldr> (we probably can assume so because apple's DTK for x86 was also underpowered compared to the machines that replaced it)
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64