<flokli>
> These are programs and libraries used at build time that produce programs and libraries also used at build time.
<{^_^}>
error: syntax error, unexpected ')', expecting ID or OR_KW or DOLLAR_CURLY or '"', at (string):436:1
<flokli>
If the dependency doesn't care about the target platform (i.e. isn't a compiler or similar tool), put it in nativeBuildInputs instead.
<flokli>
hmmh
<samueldr>
should splicing work with that? but, similarly, I guess there's no way to get splicing from stdenv's sc
<samueldr>
stdenv's cc*
<Ericson2314>
flokli: on a call but lgtm
<flokli>
no worries. approve+merge or make it a nativeBuildInput later if you have time :-)
<flokli>
I'll need to go to bed anyways
<thefloweringash>
IIUC, deps$x$y is asking for a dependency with: their host=my $x, their target=my $y. the nixpkgs documentation titled "Variables specifying dependencies" is pretty good
<thefloweringash>
The section titled "Theory of dependency categorization" with the table and examples is quite confusing though. I'm not sure if I haven't understood it, or if it's wrong.
<samueldr>
yeah, despite knowing about those sections, and having read them, if it leaves the realm of `buildInputs` and `nativeBuildInputs` I'm still confused :)
<thefloweringash>
the arrow notation "x -> y", seems like it's talking about table rows, but then the clarifying examples say "host -> build" which isn't a member of the table
bridge[evilred] has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
{`-`} has joined #nixos-aarch64
ornxka has quit [Quit: No Ping reply in 180 seconds.]
ornxka has joined #nixos-aarch64
veleiro has joined #nixos-aarch64
ib07 has quit [Ping timeout: 240 seconds]
ib07 has joined #nixos-aarch64
<veleiro>
i havent been able to compile any kernels on my pinebook pro
<veleiro>
it errors with compiling GHC 8.6.5 by Segmentation Fault
<veleiro>
tried multiple versions, 5.4, 5.7.* and 5.8.* but it continues
<veleiro>
so maybe its something to do with the nix version currently installed
<samueldr>
GHC's not part of the kernel compilation closure, so something else likely is amiss
<veleiro>
oh, thanks for the suggestion
<veleiro>
the error occurs at <nix-store-hash>-stdenv-linux/setup @ running install tests
<veleiro>
i thought it might be my use of home-manager
<veleiro>
its actually at ghc-8.6.5-binary.drv
veleiro has quit [Remote host closed the connection]
veleiro has joined #nixos-aarch64
cole-h has quit [Ping timeout: 265 seconds]
alp has joined #nixos-aarch64
orivej has quit [Ping timeout: 272 seconds]
FRidh has joined #nixos-aarch64
Dezgeg has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-aarch64
blitzclone[m] has quit [Ping timeout: 260 seconds]
blackriversoftwa has quit [Ping timeout: 260 seconds]
blitzclone[m] has joined #nixos-aarch64
blackriversoftwa has joined #nixos-aarch64
alp_ has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
Dezgeg has joined #nixos-aarch64
xtro has joined #nixos-aarch64
xtro is now known as Guest7364
Guest7364 has quit [Client Quit]
sds2 has joined #nixos-aarch64
<sds2>
Yesterday I build an image of NixOS for armv7 and after several hours it created an image in the result folder looking like this ′result -> /nix/store/<hash>-nixos-sd-image-20.09.2016.19db3e5ea27-armv7l-linux.img-armv7l-unknown-linux-gnueabihf′.
<sds2>
Questions: Why is it saying 20.09.2016? The resulting image has a timestamp of Jan 1, 1970. Its size is 734M. Is it possible to build a headless/smaller image because I intend to use NixOS only as a server and I won't need UI, desktops, sound etc.
<patagonicus>
sds2: The timestamp doesn't mean much, usually Nix will set it to fixed value so that it doesn't depend on when exactly you're building something.
<patagonicus>
Not sure about the 2016 part. But you can certainly build a smaller image, it will just need some tweaking. The sd-image stuff pulls in a few things.
<sds2>
patagonicus: Thanks a lot. Where and how can I customize what's being build to archive a smaller image? Is there a guide in the doc for this?
<patagonicus>
installation-device.nix and see if that boots. You'll have to convert the imports into ones of the form <nixpkgs/nixos/…> like the one used in armv7-linux.nix since the relative paths won't work.
<Ke>
anyone got that honeycomb yet
alp_ has quit [Ping timeout: 272 seconds]
<patagonicus>
sds2: I don't think there's a guide. I've built some stuff that custom builds images for my armv7 machines, but I wasn't worried about size. If you can find a generic "make NixOS smaller" guide you can probably apply most of that.
<patagonicus>
I'd really recommend putting your configs in version control - you can just use the cross-system git repo - and committing often. That way you'll know which change breaks something.
<patagonicus>
My guess is that installation-device alone will save you a bit, since it pulls in manuals and a full copy of the nixos channel. Once you want to go smaller it'll get more complicated.
<sds2>
patagonicus: Cool, thank you. I'm new to NixOS and I thought I can try it out on my Cubietruck and see what i can do with it. For now I will probably use the full image as is and try to get my device booting it. Then I will familiarize myself more with the whole building/compiling process. It's quite exciting... :)
<patagonicus>
Yeah, I'm still learning as well, but getting this to work has forced me to learn some things about nixpkgs, so that's a plus. :)
ardumont has quit [Ping timeout: 264 seconds]
<patagonicus>
This channel was also very helpful in getting my Odroid HC2s running. So feel free to ask if you get stuck somewhere.
zupo has joined #nixos-aarch64
ardumont has joined #nixos-aarch64
ib07 has quit [Ping timeout: 260 seconds]
<sds2>
patagonicus: Exactly. Step by step is the way to go. It's quite overwhelming at first but I will manage to learn and find out all the good stuff and how to become more sufficient with it. If I can get my device booting what I just build yesterday that would be a great leap forward... I'm sure I will have more questions though. I appreciate there is a channel to get help and guidance in the process...
<sds2>
How is the Odroid HC2 holding up with NixOS?
ib07 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<patagonicus>
Ok? Needs some customizations, including "manually" installing the bootloader (it has a package, but I had to put the install stuff into my custom scripts). Performance isn't awesome, but I haven't figured out yet if it's disk encryption, SSH encryption or networking that's the bottleneck.
<patagonicus>
It doesn't properly shut down the HDD on shutdown, which is a known issue and I haven't gotten around to adding that to my system, but it should be easy. I still need to tinker with getting it to unlock the HDD on boot, but that's not HC2 specific.
<patagonicus>
Otherwise - pretty cool devices. Got four of them as a cluster, but so far they are only used to share Nix building work, still takes half a day or so to build the system on updates. I plan to set up GlusterFS eventually.
<patagonicus>
sds2: If you do manage to get it to boot you should add it to https://nixos.wiki/wiki/NixOS_on_ARM. I've added the HC1/2 because it was missing (and that's my only NixOS Wiki edit so far).
sds2 has quit [Client Quit]
ib07 has quit [Ping timeout: 272 seconds]
sds2 has joined #nixos-aarch64
<sds2>
patagonicus: Sounds pretty cool and adventurous… :) I’m excited to see what I will run into. Sure, when I get it up and running I will add it to the ARM NixOS wikipage, no problem. I’m already documenting every tiny step of the process. I took the BananaPI as an example on how to get started. The device seems similar and I suppose I’ll have to do something similar for the Cubietruck. I also build an recent u-boot which I will flash on the SD-card
<sds2>
together with the NixOS image and see what I’ll get...
alp_ has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
ib07 has joined #nixos-aarch64
<patagonicus>
Yay, building the SD card image still works - built the image, flashed it onto a new microsd card, booted it up and it just worked. :)
<patagonicus>
Still need to fix it so that it auto-expands /. And I should include the ssh server key to my config so it's not auto-generated every time I reinstall.
<patagonicus>
Oh. I guess I never implemented adding the secrets to the machine at all, so it's also missing the keys for wireguard and the HDD. But that's an easy fix.
justanotheruser has quit [Ping timeout: 264 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
superherointj has joined #nixos-aarch64
superherointj has quit [Remote host closed the connection]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
ib07 has quit [Ping timeout: 260 seconds]
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
ib07 has joined #nixos-aarch64
ib07 has quit [Max SendQ exceeded]
ib07 has joined #nixos-aarch64
ib07 has quit [Read error: Connection reset by peer]
ib07 has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
ib07 has quit [Max SendQ exceeded]
ib07 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
FRidh has quit [Ping timeout: 264 seconds]
FRidh has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
<sds2>
patagonicus: Well, on the first try it does not boot. I unpacked my xxx.img.zstd file and used "sudo cp sd-image-armv7l-linux.img /dev/sdd" to copy the whole image over but that did not work out for the cubietruck. I guess I need to do some extra route. Maybe I need to use my compiled u-boot, creating my own boot.cmd etc and then copy the NixOS image over. Similar to here: https://archlinuxarm.org/platforms/armv7/allwinner/cubietruck#installation
justanotheruser has quit [Ping timeout: 264 seconds]
<patagonicus>
sds2: You know, I'm really not sure what cp does if the destination is a device node. But my guess is that it replaces the device node and doesn't actually write the contents to the card.
<patagonicus>
Can you see if a) you still have /dev/sdd without the card inserted and b) if so, do an an ls -alFh /dev/sdd, still without the card in the reader?
alp_ has quit [Ping timeout: 272 seconds]
ardumont has quit [Ping timeout: 240 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ib07 has quit [Ping timeout: 240 seconds]
<sds2>
patagonicus: I'm not exactly sure what you mean but I checked the sd card after the cp command finished. The card has two partitions, labled FIRMWARE and NIXOS_SD. The latter has a boot and a nix folder. Everything looks proper at first glance.
<patagonicus>
Ah, ok, yeah, then it probably worked.
<patagonicus>
I have no idea how the cubietruck works. You might have to dig around if you can find some documentation from someone porting a different distro to it.
cole-h has joined #nixos-aarch64
h0m1 has quit [Quit: WeeChat 3.0]
h0m1 has joined #nixos-aarch64
alp_ has joined #nixos-aarch64
<sds2>
patagonicus: I just switched to a bigger sd card and it works, at least I see some work and output on the screen. :)) The unpacked image is really huge (3083M). I definitely need a smaller image or a bigger card. I prefer the former one.
sds2 has quit [Quit: sds2]
<patagonicus>
Hmm. Well, part of that will be the installer. My system is 2800MB, but I'm also installing a bunch of packages (prometheus, grafana, cryptsetup, lvm, borgbackup, nfs, …).
sds2 has joined #nixos-aarch64
<patagonicus>
However, if that's your limit, don't even think about installing anything on the machine itself. :) With build dependencies my 32GB cards became a problem, so I'm upgrading to 64GB. 32GB cards are doable, but you basically have enough space for the current system + the new system, if it requires a full rebuild.
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
<sds2>
patagonicus: I 'production' I want to attach an ssd drive to the SATA port and boot from there if possible. That drive is big enough to hold some data (256G) but that's the next thing I need to figure out...
<sds2>
Right now the cubietruck seems to be busy and the output is halting at "Waiting for rootfs device /dev/sda1". Is that normal? I think there is no /dev/sda1 yet, just the attached sd card, nothing else.
<patagonicus>
That … sounds wrong.
<patagonicus>
You probably won't be able to boot from SATA, but worst case you can have just the boot partition on an SD card. Maybe even just the bootloader and /boot on SATA, dunno.
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
alp_ has quit [Ping timeout: 272 seconds]
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
ib07 has joined #nixos-aarch64
<sds2>
patagonicus: Probably there is a problem with the NAND support. I just found that in the linux-sunxi.org Wiki: "Warning: Mainline NAND support is not compatible with Allwinner NAND support and will make your existing NAND unreadable." I had an Ubuntu 16.04 with an old kernel running before and booting from ssd without a sd card present. I suppose I should be able to do this with NixOS, too. Right?
<patagonicus>
Oh, yeah, if the device can boot without an SD card present, it should be possible to do that with NixOS.
<patagonicus>
But is the NAND support referring to SD cards?
<Ke>
probably raw nand chips
<Ke>
not very common, some routers have them instead of nor
rajivr has quit [Quit: Connection closed for inactivity]
<patagonicus>
https://linux-sunxi.org/NAND starts off by saying that NAND is on-board flash. So not the SD card.
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 240 seconds]
<sds2>
patagonicus: This means the output I saw was not related to NixOS at all and the sd card was completely ignored. Now it makes sense that the device was waiting for rootfs on /dev/sda1. I need to figure out how to change this and put boot in there and NixOS on the disk, I guess.
<sds2>
Ke: Yes, the cubietruck has a raw 8Gb Nand flash chip
<patagonicus>
Ah! You checked the partitions of the card before ejecting it, right? My theory is still that you didn't write the image to the card and instead replaced the device node with the image on your host machine.
ib07 has quit [Ping timeout: 260 seconds]
disasm has quit [Quit: WeeChat 2.0]
disasm has joined #nixos-aarch64
ib07 has joined #nixos-aarch64
ib07 has quit [Ping timeout: 264 seconds]
<sds2>
patagonicus: Hmm, I checked the data on the card and it looked good to me. The card was definitely not empty. I think it just ignore the card while booting and get the stuff from the NAND and not from the card. Unfortunately, I don't remember what I did to replace the original Android with Ubuntu back in the days. I guess I need to do some research to refresh my memory again...
<patagonicus>
sds2: How did you check the card? Because I'm pretty sure the cp command you posted shouldn't work.
<sds2>
patagonicus: I just re-inserted the card reader after the cp command was done and had a look inside my file manager and also gparted.
<patagonicus>
Hmm. Ok, then maybe it's fine. I'll have to try that tomorrow.
zupo has joined #nixos-aarch64
<samueldr>
cp should work to write to a destination node
FRidh has quit [Quit: Konversation terminated!]
zupo has quit [Ping timeout: 256 seconds]
zupo has joined #nixos-aarch64
<sds2>
patagonicus: I found my mistake and now I can boot from card and see actual NixOS output and have a prompt. Hooray! I simply forgot to do this: "sudo dd if=u-boot-sunxi-with-spl.bin of=/dev/sdd bs=1024 seek=8".
<patagonicus>
Ah. Not adding the right bootloader will do that. :D
<sds2>
patagonicus: Haha, yes indeed. Stupid mistake... ;) But now I can go a bit further and try to bring it to the ssd so I can boot completely without the sd card and use my ssd drive like I did with the old Ubuntu...
<sds2>
The NixOS on ARM/Cubietruck page will look almost identical to the BananaPi except one thing for now...
veleiro has quit [Read error: Connection reset by peer]
julm has quit [Ping timeout: 256 seconds]
julm has joined #nixos-aarch64
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]