Exotic Nix Targets | 299 Members | |
| 91 Servers |
| Sender | Message | Time |
|---|---|---|
| 22 Jul 2025 | ||
| maybe someone here again who can give this a look, and has the permissions necessary to upload these 👉️👈️? been using them for the last 3 weeks, so they work fine on the target in question. https://github.com/NixOS/nixpkgs/pull/423133 | 14:45:35 | |
| * maybe someone here again who can give this a look, and has the permissions necessary to upload these 👉️👈️? been using them for the last 2 or so weeks, so they work fine on the target in question. https://github.com/NixOS/nixpkgs/pull/423133 | 14:46:18 | |
| 20:38:54 | ||
| 23 Jul 2025 | ||
| 10:13:58 | ||
| 10:58:11 | ||
| 11:21:56 | ||
| 24 Jul 2025 | ||
| 10:07:02 | ||
| 25 Jul 2025 | ||
| 05:02:03 | ||
| 05:10:21 | ||
| 05:10:33 | ||
| 26 Jul 2025 | ||
| I'm interested in trying to do a cross compile from a standard It seems tricky: how can nixpkgs distinguish the build and host toolchains in the PATH when they have the same triple? My intent is to use a 'cross' build setup so that I don't have to build the whole world with my arch settings, but just the things required for runtime. Anyone got experience or thoughts on this? John Ericson | 11:42:04 | |
| IIRC it's not so much that Nixpkgs doesn't distinguish but that GNU doesn't | 12:17:34 | |
| Autoconf assumes that cross compiling is when the triples don't match | 12:17:56 | |
| Is this insurmountable? Does it mean the only solution is to do a non-cross build-the-world-from-scratch? | 12:32:36 | |
| Just overlay individual packages? | 12:33:16 | |
| Also, have you benchmarked this, like, at all? | 12:33:24 | |
| It's not about benchmarking for me. It's about architectural features. | 12:33:37 | |
| Because it's extremely unlikely you'll get significantly better performance from doing that | 12:33:40 | |
| And it's not about individual packages | 12:33:41 | |
| What "architectural features"? | 12:33:51 | |
| We're talking about things like hardening features for example. pac-ret being one example. | 12:33:58 | |
| So I was hoping to do a cross build where out pops a hardened glibc when I request... firefox. As a contrived example. | 12:34:31 | |
| What is frustrating is that it seems very close to working, but for the depsBuildBuidl = [ buildPackages.stdenv.cc ] situation. Lots of things do build as expected. | 12:35:25 | |
| You could hack it to be a different triple | 12:35:50 | |
| I was wondering about this. | 12:35:58 | |
| aarch64-pc-linux-gnu or aarch64-redhat-linux-gnu would probably work :P | 12:36:14 | |
| I have to go AFK but will be on my phone and a bit slower to respond. Back to keyboard typing in a few hours. | 12:36:21 | |
| Nice idea, I'll definitely give that a look. | 12:36:41 | |
| Hopefully I can put whatever I want in the vendor position. | 12:36:53 | |
| ... what if we make that useless vendor portion a hash of the platform? :P | 12:37:04 | |