| 12 May 2022 |
 matthewcroughan - nix.how | I thought that altered the nix store path, meaning it couldn't be used as expected | 02:43:04 |
| matthewcroughan - nix.how | when you use a cross-compiler, that's changing the inputs, therefore the output path right? | 02:43:16 |
 Zhaofeng Li | Yeah, that way you can't do stuff like nix-shell -p | 02:44:35 |
| matthewcroughan - nix.how | There's no way around that, that wouldn't break Nix, is that right? | 02:44:52 |
| matthewcroughan - nix.how | Even if you have a content addressed store, should we always expect the output of a cross-compiler to differ from native? | 02:45:11 |
| Zhaofeng Li | Not really sure for content-addressed store, maybe that's something that can be looked at. With the current setup the derivation names for native and cross are different. | 02:47:59 |
| matthewcroughan - nix.how | So does that mean we can compile images and boot them, but once booted we can't do anything with nix on the board? | 02:48:52 |
| matthewcroughan - nix.how | without waiting for the crawl of stdenv native | 02:49:05 |
| matthewcroughan - nix.how | I mean, the only way to really solve that is to have a proper build farm that just builds natively, right? | 02:49:47 |
| matthewcroughan - nix.how | If I can buy any hardware that helps with that, let me know. | 02:50:03 |
| 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 |
