jackdk has joined #nixos-aarch64
jackdk_ has joined #nixos-aarch64
jackdk has quit [Disconnected by services]
jackdk_ is now known as jackdk
zupo has joined #nixos-aarch64
<NickHu> Ok so I got this build failure: https://paste.xinu.at/UPbiBq/ in gcc; what can I do to look at the full log?
<sphalerite> NickHu: nix log '/nix/store/bp1p5sz4wh5bznf23qa63gasc3gza5m2-gcc-7.4.0.drv'
<NickHu> It says no build log available, I must have to set keep-failed somewhere
<NickHu> It's not in man nix.conf though
jackdk has quit [Ping timeout: 240 seconds]
<sphalerite> NickHu: oh, this is with nixos-install?
<sphalerite> NickHu: try adding `--store /mnt` to the command
<NickHu> sphalerite: Why does that help?
<sphalerite> NickHu: because nixos-install builds the system directly in the target filesystem, so the logs end up in the target filesystem too
<NickHu> sphalerite: Ah, I thought you meant to the nixos-install command
<sphalerite> oh, hehe :)
<NickHu> Still says build log not available
<NickHu> But I can see the logs of things which did successfully build
<NickHu> It would be nice if I could see the whole output of nixos-install like it used to; I don't remember it doing everything in a single line like this before
<NickHu> I guess I'll try to build with only 1 job and 1 core
<NickHu> I feel like that breaks gcc bootstrapping sometimes
zupo has quit [Remote host closed the connection]
<NickHu> Fresh failure: https://paste.xinu.at/a3nC/
<NickHu> Is there a way of running nix-build relative to /mnt so I can just try to build the failed gcc with --keep-failed?
<sphalerite> NickHu: pass `--store /mnt` to nix-build :)
<NickHu> sphalerite: ah, it wasn't in the manpage
<NickHu> I've run nix-build --store /mnt --keep-failed /nix/store/bp1p5sz4wh5bznf23qa63gasc3gza5m2-gcc-7.4.0.drv... we'll see what it says
<NickHu> Is there a plan to deprecated nix-env, nix-build, nix-shell etc. in favour of the new nix binary?
<sphalerite> --store is one of the options that can be used with all the commands
<sphalerite> it should probably be in man nix.conf
<sphalerite> (it isn't)
<sphalerite> NickHu: yes, but consider the warning all the nix commands have in their help messages ;)
<NickHu> I haven't seen any warning like that
<sphalerite> also the fact htat nix-env and nix-shell don't have replacements in it yet
<sphalerite> Note: this program is EXPERIMENTAL and subject to change.
<sphalerite> it's still considered an unstable interface
<sphalerite> so nix-instantiate and friends are still the canonical interface to nix
<NickHu> Ah, you meant the new nix binary - I have basically never used it haha
<sphalerite> ah right
<NickHu> Is the motivation for it just to be able to relocate the store?
<sphalerite> for --store? Or for the new nix command?
<NickHu> New nix command
<sphalerite> NickHu: no, that can be done with the old tools as well by passing --store (although it's a key feature of nix 2.0)
orivej has quit [Ping timeout: 250 seconds]
jtojnar has joined #nixos-aarch64
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 250 seconds]
orivej has joined #nixos-aarch64
<sphalerite> gchristensen: how about that reboot? ;)
<sphalerite> (or, permission to do it myself? Nobody seems to have anything running besides myself)
<gchristensen> go ahead
<sphalerite> gchristensen: I think I broke it, or how long does it take to boot?
<gchristensen> a while :)
<sphalerite> ah ok
<sphalerite> oh yeah there it is
<gchristensen> it takes a long time for the kernel to initialize all those cores
<sphalerite> haha
<gchristensen> (not kidding, although it spends more time in EFI ;))
<samueldr> the more it looks like a server, the longer it takes to boot :)
<gchristensen> haha, yeah
<sphalerite> yeah I just looked at the journal to check, it's only a matter of a second or two AFAICT?
<sphalerite> but yeah, classic server firmware…
<gchristensen> to be honest, I'm pretty sure if they unplugged the console cable (virtual and real) I think it'd boot much faster
<samueldr> my latest computer's EFI (not even coreboot+tianocore) is less than 1s for the firmware, while the workstation computer I used to use spends ~1min in the firmware before continuing with EFI boot
<gchristensen> the hardware's boot stage 0 prints a novel worth of of debug messages
<gchristensen> you can tell they really printf-debugged the hell out of it
<sphalerite> samueldr: nice! What hardware?
<samueldr> my screens take longer for waking up than the bios loads!
<samueldr> an older Zotac-branded box with an haswell-era CPU
<sphalerite> cool
<samueldr> not even recent; got it on our local craigslist-like for a good price considering the ram+storage... and it's much more silent than the workstation
<sphalerite> this makes me want to try and improve the nano pi's boot process again…
<samueldr> and can plug three screens into it, while the workstation I hadn't yet shelled out the money for a GPU able to handle them
<sphalerite> currently it has way too many stages — u-boot loads linux with vendor initramfs, linux mounts sd card root fs, which has a custom init script that loads zfs, then imports the pool that has the real root filesystem on it and switch_roots into it
<gchristensen> samueldr: dang, that looks almost NUC-ian
<samueldr> yeah
<samueldr> though the bios being quick is just plain luck I guess
<samueldr> I'm a 18650 away from the pinephone devkit being ready to be used
orivej has quit [Ping timeout: 250 seconds]
<gchristensen> (first I thought that was price, then baud, then cable, then DDG'd it and now realize: battery) nice!
orivej has joined #nixos-aarch64
<samueldr> though there's one annoying issue with the current devit; the SPI Flash accidentally shares the chip-select line with another component; the other component given priority
<gchristensen> oops...
<samueldr> what it means is that stock, it can't be flashed with u-boot outside the storage devices
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
<andi-> what kind of a flash chip is it? Can't you use a SOIC/SOP/… clip?
<samueldr> the issue isn't with flashing, it's that the board isn't able to use it :)
<andi-> ohh
<andi-> /o\
<samueldr> when it tries to access the NOR flash memory it ends up using the light led flash
<andi-> nice feature :D
<samueldr> I wonder if they got confused on "flash" when figuring out the lines
<andi-> I really hope that by the time I get to play with my librem5 someone has put all the energy into a mobile port of nixos + UI or I have lots of spare time (and money)...
<andi-> I am a bit skeptical regarding the memory available on both the pine64 phone and the librem... 2/3GB of RAM.. Years ago that was plenty. How will the webborwsers chope with that? It has been too many years on overpowered laptops/workstations to still have a feeling bow bad it is these days..
<samueldr> the pinephone though has one thing for itself: it's intended to be dirt cheap, but yeah, memory is going to hurt it still :/
<samueldr> (there is some hope that it might be 3GB, but they don't want to say anything over 2GB until it's sure it can be done both technically and financially)
<samueldr> IIRC, so "it's 2GB" as far as I'm concerned
<andi-> Updating the device will be funny.. either it still fits, you have to use swap for a nix eval or just copy a new /nix/store (incrementally?) to update..
<samueldr> ¯\_(ツ)_/¯ I'm more concerned with 16GB space for the pinephone, which I think will be handled by out-of-band system generation since some android device also have that limitation
<samueldr> and with android-based devices being in more of a tough spot with predetermined untouchable partitions, of which "system" (though we can also use userdata instead) is about 3GB
<andi-> time will tell :-)
Thra11 has joined #nixos-aarch64
{`-`} has joined #nixos-aarch64
feepo has quit [Read error: Connection reset by peer]
feepo has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 255 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<NickHu> I'm getting the craziest build error now: https://paste.xinu.at/1Nrz/ - but the archive extracts fine when I do it myself! 06be9865c6f418d851ff4494e12406568353b891ffe1f596b34693c387af26c7 /nix/store/0fpf4zfxzkz5yxcdp4wbyy1z52yzj1kw-acl-2.2.53.tar.gz
<NickHu> Has anyone ever encountered something like this before?
<samueldr> /tmp getting tight?
<samueldr> only a wild guess
<gchristensen> I can't do it Very Soon, but I can some-day try to make tmp bigger
<gchristensen> also,what if tmp was not on a tmpfs, isn't that an easy option?
<gchristensen> someone send me a PR :)
<gchristensen> oh, the ro/rw split is on /nix :/
<samueldr> no, sorry, I was guessing at NickHu's problem
<gchristensen> at any rate, very happy to merge PRs making the builder better :P
jackdk has joined #nixos-aarch64