| 14 Nov 2022 |
 pie_ | It would be nice if why-depends had a mode that didn't require a successful build... | 13:47:55 |
| pie_ | Though I imagine it's probably related to one of these.
these 5 derivations will be built:
/nix/store/2spfjgh2vpn9r6yk4yw082943rci8jjx-zstd-static-x86_64-unknown-linux-musl-1.5.2.drv
/nix/store/4f54gwg5jhknxdpgfcayp4k76nyv3w64-util-linux-static-x86_64-unknown-linux-musl-2.37.4.drv
/nix/store/nam1fgzycp7viggn8xphdac43f9ana0j-e2fsprogs-static-x86_64-unknown-linux-musl-1.46.5.drv
/nix/store/y5f3dr38vmzn3d24ialzrn09w88yrqhj-libarchive-static-x86_64-unknown-linux-musl-3.5.3.drv
/nix/store/32l2s1szabqzgij3g9yx0za2zmlriyna-proot-static-x86_64-unknown-linux-musl-5.2.0.drv
| 13:49:29 |
| pie_ | Though those could also just be fails somewhere in the deptree :/ | 13:50:05 |
| pie_ | per nix-store -q --tree its proot -> libarchive -> e2fsprogs -> util-linux (I think) | 13:53:53 |
| pie_ | but I dont understand why proot is depending on libarchive | 13:54:03 |
| pie_ | Its not directly specified in the nix expression afaict. | 13:54:13 |
| pie_ | Well, I'm stumped. | 16:06:50 |
| pie_ | Ok, this is terrible and I still have no idea why things are the way they are, but earlier today I got this to work: | 22:50:06 |
| pie_ | * Ok, this is terrible and I still have no idea why things are the way they are, but earlier today I got this to build: | 22:50:11 |
| pie_ | nix-build --option max-jobs 1 --option cores 1 -I nixpkgs=channel:nixos-21.11 -E "with import <nixpkgs> { overlays = [ (self: super: { libarchive = super.libarchive.override (o: { e2fsprogs = super.hello; }); }) ]; }; (pkgsStatic.proot.override (o: { enablePython = false; })).overrideAttrs (o: { preUnpack = ''export PATH=\"\$PATH\":\${pkgsStatic.pkg-config}/bin;\${git}/bin''; })" | 22:50:41 |
| pie_ | (literally. It can probably be cleaned up a bit.) | 22:51:01 |
| 15 Nov 2022 |
| pie_ | Ok, the next problem is I cant seem to run anything because the dynamic linker fails
| 02:01:19 |
| pie_ | newfstatat(3, "", 0x7fffe4a41460, AT_EMPTY_PATH) = -1 EINVAL (Invalid argument)
Turns out:
AT_EMPTY_PATH (since Linux 2.6.39)
I'm on 2.6.32
| 02:02:12 |
| pie_ | * Ok, the next problem is I cant seem to run anything because the dynamic linker fails
| 02:02:34 |
| pie_ | *
Ok, the next problem is I cant seem to run anything because the dynamic linker fails | 02:02:44 |
| pie_ | And I'm not sure what to do here again | 02:03:08 |
| pie_ | (besides ask for a kernel upgrade...) | 02:03:22 |
| pie_ | I could possibly try building things with an earlier libc I suppose | 02:03:59 |
| pie_ | though also thats basically rebuild the world afaik | 02:04:17 |
| pie_ | well, modulo some hacks, I think using musl is working | 20:26:15 |
| pie_ | * well, modulo some hacks, I think using musl is working (pkgsMusl) | 20:26:29 |
| pie_ | heh, ran into this too https://github.com/NixOS/nixpkgs/issues/29778 with lustre.lov ; -> https://nixos.org/manual/nix/stable/command-ref/conf-file.html see ignored-acls | 20:34:26 |
| pie_ | running into some dynamic linking issues with nix-shell, not sure about the cause | 21:09:59 |
| pie_ | going to try to get a dynamically linked nix on there now that I have static nix at least capable of builds | 21:10:19 |
| pie_ | oh you know what, maybe I didnt make the static-nix with musl | 21:16:50 |
| pie_ | though IDK why that would be a problem when nix-shell is used | 21:17:02 |
| pie_ | ok the problem is that the builder of pkgsStatic.hello for example isnt using the bash from pkgsStatic, its using it from the normal stdenv i thi | 23:40:24 |
| pie_ | * ok the problem is that the builder of pkgsStatic.hello for example isnt using the bash from pkgsStatic, its using it from the normal stdenv i thik | 23:40:27 |
| pie_ | * ok the problem is that the builder of pkgsStatic.hello for example isnt using the bash from pkgsStatic, its using it from the normal stdenv i think | 23:40:29 |
| pie_ | ok I figured out the / part of the problem is that nix-shell invokes stdenv.mkShell implicitly with -p so that's where that bash is coming from | 23:47:43 |
