28 Apr 2025 |
rhelmot | if you submit a patch I'll test it | 06:18:25 |
Alyssa Ross | lib.meta.availableOn pls | 06:43:48 |
Artturin | Maybe like this availableOn pkgs.stdenv.buildPlatform wine | 06:47:09 |
Artturin | Or wine.stdenv.buildPlatform | 06:48:39 |
FliegendeWurst | funny error message I just got: checking bits per byte... configure: error: failed to compile test program Interestingly enough it does use the detected value in a sensible way, in exactly two places.. but I'd bet it assumes 8 bits/byte in at least one other place. | 22:09:11 |
29 Apr 2025 |
Grimmauld (any/all) | when will we have cross-compilation for WITCH, the computer that does 9 bits per byte (sign + 8 actual bits) | 06:44:23 |
rosssmyth | Or the Apollo Guidance Computer, which was 15 bits per word (which is for all intents and purposes a byte) | 16:28:46 |
K900 | /me laughs in Setun | 16:29:30 |
K900 | 18 trit per word | 16:29:41 |
K900 | Yes, trit | 16:29:44 |
1 May 2025 |
| Rosuavio changed their display name from Rosario Pulella to Rosuavio. | 20:08:33 |
| oak 🏳️🌈♥️ changed their display name from oak - mikatammi.fi to oak 🫱⭕🫲. | 23:18:35 |
6 May 2025 |
rosssmyth | I was messing around trying to see if I could build a stdenv with gcc-arm-embedded last night. Feels like it should be possible, but I'm unsure of the exact incantation to do so. I'm starting with an embedded stdenv, then trying to override it.
The first issue that apparently cc-wrapper complain if your target platform is not linux or darwin, so I have to pass NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM . Whether this is actually unsupported or not I'm unsure.
I've tried it two ways: One using pkgs.wrapCCWith { stdenvNoCC = pkgsCross.stdenvNoCC; } and one with pkgsCross.wrapCCWith . The former got me closer, but for some reason the wrapper were not being symlinked to the bin dir. Looking at the source I tried a few things, but was unsuccessful in getting it to work. The latter fails because even though I'm trying to make a nolibc wrapper, the gcc wrapper seems to try and access libc directories at pkgs/development/compilers/gcc/common/configure-flags.nix:112:31 , resulting in a cannot coerce null to string .
You can find my progress so far here: https://github.com/RossSmyth/armRepro/tree/NativeWrap https://github.com/RossSmyth/armRepro/tree/EmbedWrap
If anyone has tried this in the past, let me know if you may know how to wrangle it into shape
| 16:50:03 |
7 May 2025 |
| Aerden joined the room. | 07:55:08 |
szlend | is there any way to get a pkgs instance where buildPlatform != hostPlatform != targetPlatform? | 20:30:56 |
Alyssa Ross | I don't think so | 20:37:40 |
szlend | I'm trying to map how pkgs<host><target> packages are offset inside another pkgs<host><target> and it would really help with understanding | 20:58:45 |
szlend | it don't actually need to build anything | 20:59:51 |
K900 | Are you trying to do Canadian cross | 21:09:37 |
K900 | Also can we PLEASE kill targetPlatform | 21:09:43 |
K900 | Yes I will keep bringing this up | 21:09:50 |
szlend | I'm trying to wire up a spliced package set with makeScopeWithSplicing that is not overlayed on top of pkgs . Usually you would wire it up with generateSplicesForMkScope , but that's not an option here. You can wire up otherSplices naively with recursion, but that explodes evaluation very quickly, as it unnecessarily evaluates against the same pkgs<host><target> instances. | 21:20:43 |
SomeoneSerge (UTC+U[-12,12]) | I was very stupidly confused about this even though there are only two kinds of "offsets" in the end. I just couldn't figure out which sense is meant in any particular place. TLDR: Offsets in Nixpkgs manual are points, but {host,target}Offset s in setup-hook s are vectors | 21:21:51 |
szlend | This is my understanding of how perspective shifts, but I could be very wrong: https://gist.github.com/szlend/62bfa710ff89b7dc3a871693ca34c94c | 21:22:38 |
szlend | So I kinda wanna confirm it :D | 21:22:45 |
SomeoneSerge (UTC+U[-12,12]) | Does root refer to the current derivation? | 21:25:44 |
K900 | Can you not overlay it on pkgs? | 21:27:35 |
szlend | I'm thinking about it like root == pkgsCross.<platform> == pkgsCross.<platform>.pkgsHostTarget (assuming those are equivalent) | 21:27:44 |
szlend | so pkgsCross.<platform>.pkgsBuildHost.pkgsBuildTarget == pkgsCross.<platform>.pkgsHostHost | 21:28:39 |
szlend | * so pkgsCross.<platform>.pkgsBuildHost.pkgsTargetTarget == pkgsCross.<platform>.pkgsHostHost | 21:28:57 |