| 11 Apr 2025 |
 Alex | In reply to @dramforever:matrix.org
i don't remember having this problem... Possibly because you're on a version after fgaz changed nixpkgs to disable the check when GHC is not available on the platform but before my changes to GHC for full cross-compilation support.
I had to break fgaz's fix otherwise you couldn't cross compile to platforms not already available as bindists from upstream. | 07:51:03 |
| Alex | In reply to @michal:tar.black
Out of morbid curiosity I genuinely blanked out everything except the filesystem declarations in hardware-configuration.nix and just the hostname in configruation.nix and somehow it still complained about it Default empty configuration won't work. | 07:52:04 |
 dramforever | you can bring in an overlay (completely untested)
(final: prev: {
writeShellApplication = args:
let
replace =
if (args.checkPhase or null) == null
then
{
checkPhase = ''
runHook preCheck
runHook postCheck
'';
}
else
{};
in
prev.writeShellApplication (args // replace);
})
| 07:52:45 |
| dramforever | the "easier said than done" you mentioned before | 07:53:10 |
| dramforever | this is pretty hacky though | 07:54:03 |
| dramforever | or you can see if you can update your nixpkgs to after the ghc availability check | 07:54:30 |
 Michal | Yeah, I was ideally hoping to get a simple configuration.nix going with networkmanager and openssh at the very least so i can reliably connect to wifi and ssh in- that way I can port the config to my flake and deploy from there, which would let me pin to a specific version | 07:56:26 |
| dramforever | it would be far easier to cross compile it on the host anyway... | 07:56:59 |
| Michal | Yeah at the end of the day that might just be what I have to do | 07:57:27 |
| Michal | I was hoping to be able to deploy from the machine directly and use a binary cache to speed things up, but this way I assume I'll probably have to build an SD image each time? | 07:57:59 |
| Michal | (Since I'm using the SD card for now, that is) | 07:58:08 |
| Alex | In reply to @dramforever:matrix.org
it would be far easier to cross compile it on the host anyway... Not necessarily. Cross is broken for a large number of packages. | 07:58:10 |
| dramforever | that is true but i really doubt native is better | 07:58:27 |
| dramforever | and one of them is like twenty times faster than the other | 07:59:06 |
|  Jnk 📎 joined the room. | 10:40:03 |
| dramforever | jokes on me, i think home-assistant-chip-wheels might actually be impossible to cross | 14:09:57 |
| dramforever | basically one of the steps of home-assistant-chip-wheels is to pip-compile (from piptools) a requirements file to lock it down | 14:13:24 |
| dramforever | (actually something like python3 --module piptools compile) | 14:13:59 |
| dramforever | however, i'm pretty sure there is no way to convince pip-compile to use a platform that is not the build platform | 14:14:30 |
| 12 Apr 2025 |
 misuzu | In reply to @alex:tunstall.xyz
Possibly because you're on a version after fgaz changed nixpkgs to disable the check when GHC is not available on the platform but before my changes to GHC for full cross-compilation support.
I had to break fgaz's fix otherwise you couldn't cross compile to platforms not already available as bindists from upstream. https://github.com/NixOS/nixpkgs/issues/231537#issuecomment-2745384196 | 06:45:52 |
| Alex | Oh nice, a new fix is merged (2024-12-08). | 06:50:33 |
|  oak changed their display name from oak to oak - mikatammi.fi ÄÄNESTÄ. | 12:11:51 |
| oak changed their profile picture. | 12:13:45 |
 implr | I didn't see your message earlier but I also came up with a stupider version of this in https://github.com/NixOS/nixpkgs/issues/397769, then also a pip error | 13:31:42 |
| oak changed their display name from oak - mikatammi.fi ÄÄNESTÄ to oak - mikatammi.fi. | 12:56:20 |
| dramforever | yes, my understanding is that the pkg-config patch is correct, whereas this piptools error is much more inherent | 13:32:41 |
| dramforever | essentially, piptools just does not support cross at all | 13:33:10 |
| dramforever | https://github.com/jazzband/pip-tools?tab=readme-ov-file#cross-environment-usage-of-requirementsinrequirementstxt-and-pip-compile
As the resulting requirements.txt can differ for each environment, users must execute pip-compile on each Python environment separately to generate a requirements.txt valid for each said environment.
| 13:33:22 |
| 14 Apr 2025 |
|  @senk0:element.senk0.com joined the room. | 00:37:04 |
|  Kilometers joined the room. | 01:29:18 |
