| 14 Feb 2025 |
 rosssmyth | Yeah that's what I was hoping it would set 😅. | 19:00:10 |
 Artturin | stdenv = overrideCC stdenv (buildPackages.wrapCC (stdenv.cc // { stdenv.cc.targetPlatform = stdenv.cc.targetPlatform // { gcc = stdenv.cc.targetPlatform.gcc // { arch = "arv6m"; cpu = "cortex-m0"; thumb = true; }; }; })) | 19:07:09 |
| Artturin | * stdenv = overrideCC stdenv (buildPackages.wrapCC (stdenv.cc // { stdenv.cc.targetPlatform = stdenv.cc.targetPlatform // { gcc = stdenv.cc.targetPlatform.gcc // { arch = "arv6m"; cpu = "cortex-m0"; thumb = true; }; }; })); | 19:07:11 |
| Artturin | Should work if the gcc flags aren't really needed | 19:08:06 |
| Artturin | * Should work if the gcc build flags aren't really needed | 19:08:51 |
| rosssmyth | If I put that in my default.nix it results in an infinite recursion. My plan with this is to be able to build for both the armv6m target and my x86 host as I have tests that meson runs as well. I am currently using the arm-embedded-gcc packages in a noCC derivation. | 19:17:36 |
| Artturin | Change the variable name or put it in the callPackage overrides | 19:18:36 |
| Artturin | callPackage ./file.nix { <here> | 19:18:47 |
| Artturin | * callPackage ./file.nix { <here> } | 19:18:49 |
| rosssmyth | It still errors with infinite recursion. I have it setup as
highPower = with armPkgs;
callPackage ./default.nix {
stdenv = with pkgs;
overrideCC stdenv (buildPackages.wrapCC (stdenv.cc
// {
stdenv.cc.targetPlatform =
stdenv.cc.targetPlatform
// {
gcc =
stdenv.cc.targetPlatform.gcc
// {
arch = "arv6m";
cpu = "cortex-m0";
thumb = true;
};
};
}));
};
| 20:04:05 |
| rosssmyth | oh wait | 20:04:14 |
| rosssmyth | I think I see the error | 20:04:26 |
| rosssmyth | * It still errors with infinite recursion. I have it setup as
highPower = with armPkgs;
callPackage ./default.nix {
stdenv =
overrideCC stdenv (buildPackages.wrapCC (stdenv.cc
// {
stdenv.cc.targetPlatform =
stdenv.cc.targetPlatform
// {
gcc =
stdenv.cc.targetPlatform.gcc
// {
arch = "arv6m";
cpu = "cortex-m0";
thumb = true;
};
};
}));
};
| 20:05:06 |
| rosssmyth | No, I don't | 20:06:35 |
| Artturin | Look through the trace | 20:17:09 |
 alexfmpe | In reply to @emilazy:matrix.org
fwiw still personally happy to mentor bringing iOS support up to date in line with my previous statements about how it should work :P I remember, it's just taking longer than I expected to get through pkgsCross.ghcjs so not enough budget yet for iOS | 20:26:24 |
| alexfmpe | There's also the, heh, cross cutting concern of template haskell | 20:27:09 |
| rosssmyth | That still ends up building it in ARM mode. Oh well. | 20:44:36 |
|  lucassong joined the room. | 20:53:29 |
| lucassong | hello | 20:53:47 |
| 15 Feb 2025 |
| alexfmpe | hmm the types.h errors are gone in staging-next, someone must have fixed something in between | 00:45:47 |
| alexfmpe | though android-ndk-toolchain fails from the recent noBrokenSymlinks | 00:46:23 |
| alexfmpe | * though android-ndk-toolchain still fails from the recent noBrokenSymlinks | 00:57:01 |
| alexfmpe | ah yeah no false alarm, I was building the wrong thing, the types.h and other errors are present in staging(-next) | 01:06:05 |
| alexfmpe | fixed this one at least: https://github.com/NixOS/nixpkgs/pull/382182 | 01:23:07 |
|  BenjB83 joined the room. | 10:14:34 |
| BenjB83 changed their display name from Benjamín Buske to BenjB83. | 10:43:28 |
| 16 Feb 2025 |
|  KristijanZic joined the room. | 01:07:04 |
|  Jake Hillion joined the room. | 18:26:31 |
| 17 Feb 2025 |
 Axman6 | If you're building on a x86_64-linux system and you build pkgs.pkgsCross.gnu64.foo is there a difference between what it builds and what pkgs.foo? are there any checks that a cross compile isn't actually a cross compile? | 06:11:55 |
