Nix Cross Compiling | 579 Members | |
| 129 Servers |
| Sender | Message | Time |
|---|---|---|
| 21 Apr 2025 | ||
| But the original PR just works basically | 00:40:12 | |
| 🤷 | 00:40:27 | |
| oh i didn't realize you were testing a PR | 01:22:05 | |
| I'm picking up development of the PR, I hope to fix it in 25.05 | 04:54:32 | |
| 04:58:48 | ||
| wait can't i use pkgsCross to compile from aarch64 for x86_64-linux? | 06:57:46 | |
| You can unless cross blows up | 06:57:57 | |
| its not listing as something in the attrset | 06:58:57 | |
| 06:59:34 | |
It's pkgsCross.gnu64 | 06:59:51 | |
| The subset names are stupid | 06:59:56 | |
| huh | 07:00:21 | |
| thanks | 07:00:23 | |
| time to test whether i can build apparmor as cross now | 07:01:51 | |
| I am working on https://github.com/NixOS/nixpkgs/pull/400430 Everything works, except apparmor-pam. That one doesn't find the pkg-config things. It was broken before too, i didn't break it - but i'd love to fix it! Any ideas? | 09:41:41 | |
| Relevant log:
| 09:51:14 | |
is this because it tries to run target pkg-config instead of build machine pkg-config, maybe? | 09:53:03 | |
* is this because it tries to run target pkg-config instead of build machine pkg-config, maybe? (building x86_64 from aarch64) | 09:55:58 | |
| Ok, might be fixed | 10:03:55 | |
| 13:27:04 | ||
we set PKG_CONFIG etc. variables for cross | 13:44:17 | |
| https://github.com/NixOS/nixpkgs/pull/400430/files#diff-def63f7c5751b7e899bdb59c3eea509acb9e4bac8a02a281ec588127c37b988cR16-R19 yeah, marcin-serwin saw the issue and i got it fixed | 13:48:38 | |
| Now all of apparmor supports cross, LLVM, and Musl | 13:49:20 | |
| packaging looks clean, nice | 13:54:56 | |
| Thank you, better than whatever this was: https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/os-specific/linux/apparmor/default.nix But i do expect some review to still come along and request some change because of some oversight. Building my system against this is not viable as it rebuilds systemd and dbus | 14:05:41 | |
| there comes a time in every Nixpkgs contributor's life where they must purchase a Big Computer | 14:06:20 | |
| 15:18:56 | ||
I have a job that runs my builds against latest unstable each weekend, and this weekend the bump from GCC 14.2.1 20241116 to GCC 14.2.1 20250322 has changed something with relocations as I now get a bunch of dangerous relocation: unsupported relocation. Mainly because relocations are not supported on the target I used (arm-embedded, armv6-m), but I pass in hardeningDisable = [ "all" ];. I expected something to break due to the bump based upon that issue about GCC breakage, but not this. Anyone have any ideas what may have changed? | 16:42:03 | |
In reply to @rosssmyth:matrix.orgWhat derivation broke? | 17:17:44 | |
| Do you have an easy reproducer? | 17:17:58 | |