| 12 May 2022 |
 matthewcroughan - nix.how | Can't wait to get my board :D | 02:51:13 |
| matthewcroughan - nix.how | It is incredibly impressive how much has been done in the past few months by you | 02:51:53 |
| matthewcroughan - nix.how | * It is incredibly impressive how much has been done in the past few months by you and others | 02:52:02 |
 Zhaofeng Li | In reply to @matthewcroughan:defenestrate.it
So does that mean we can compile images and boot them, but once booted we can't do anything with nix on the board? You can develop on your x86 box, and push the closure to the board | 02:57:22 |
| Zhaofeng Li | In reply to @matthewcroughan:defenestrate.it
I mean, the only way to really solve that is to have a proper build farm that just builds natively, right? That would be the way forward, but right now there aren't boards that are strong enough to not be painful for large packages | 02:59:44 |
 Julio Sueiras | 
Download Screenshot from 2022-05-11 23-13-36.png | 03:13:56 |
| Julio Sueiras | k, in the system now =) | 03:14:00 |
| Julio Sueiras | right now working on patching/getting ghc to work | 04:27:02 |
| Julio Sueiras | since it seem that nix itself uses a binary ghc 8.10.7 for bootstrapping later ghc | 04:27:28 |
 Rick (Mindavi) | In reply to @matthewcroughan:defenestrate.it
Even if you have a content addressed store, should we always expect the output of a cross-compiler to differ from native? I give it a good chance it'll differ, but only one way to find out :) | 05:18:32 |
| Rick (Mindavi) | It does help that the same compiler (gcc) is used, I'd say | 05:19:25 |
| 13 May 2022 |
|  Janne Heß joined the room. | 12:08:21 |
| Janne Heß | Fyi, Hydra will not properly work on non-x86 and non-aarch64 anymore: https://github.com/NixOS/nixpkgs/pull/172378/files#diff-b8f33964a93f34e19fdee3d032e64396c384b7b652f1e167a708b21ab79a0ba9R24500 | 12:09:00 |
| Janne Heß | Letting you know to save you from wasting your time with troubleshooting | 12:09:20 |
| Rick (Mindavi) | Luckily the tests from UUID4-Tiny will alert you to that | 12:19:09 |
| Rick (Mindavi) | But yeah, I really hope it'll be replaced with a dependency that's a bit more cross-platform | 12:19:37 |
| Janne Heß | Now that I think of it… why are we not calling gcc in the postPatch phase? | 12:19:47 |
| Janne Heß | (the call from your comment) | 12:20:00 |
| Rick (Mindavi) | It'd need some cleanup of the output, but definitely an option! | 12:23:27 |
| 17 May 2022 |
|  v0|d joined the room. | 18:04:30 |
 qbit | matthewcroughan - nix.how: out of the gate, bootstrap.sh fails | 19:27:37 |
| qbit | configure.ac:1: warning: AC_INIT: not a literal: "m4_esyscmd(bash -c "echo -n $(cat ./.version)$VERSION_SUFFIX")"
configure.ac:108: error: possibly undefined macro: AC_MSG_ERROR
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf-2.71: error: /usr/local/bin/autoconf-2.71 failed with exit status: 1
| 19:27:42 |
| qbit | ill try the release'd version (with the configure script) - but it fails too iirc | 19:28:08 |
| matthewcroughan - nix.how | do things as specified in hacking.md | 19:28:18 |
| qbit | is that not the first step? | 19:28:49 |
| qbit | it is :P | 19:28:52 |
| matthewcroughan - nix.how | You need to get the correct dependencies though. | 19:29:07 |
| qbit | To build Nix itself in this shell:
[nix-shell]$ ./bootstrap.sh
[nix-shell]$ ./configure $configureFlags --prefix=$(pwd)/outputs/out
[nix-shell]$ make -j $NIX_BUILD_CORES
| 19:29:07 |
| matthewcroughan - nix.how | Which is usually waht nix develop will do. | 19:29:11 |
| qbit | i have them | 19:29:13 |
