| 19 Feb 2025 |
 K900 | (again) | 09:51:12 |
 @rick:matrix.ciphernetics.nl | Probably yeah | 10:57:31 |
| K900 | All right, let's see if it blows up this time | 11:05:21 |
| 20 Feb 2025 |
|  tobim joined the room. | 09:58:16 |
 p14 | I'm seeing something quite weird with gmpxx whereby it will succeed/fail at the configure stage checking build system compiler gcc... yes based on something bogus in the environment. I'm wondering whether its success/failure is actually conditioned on something arbitrary relating to what's in the environment somehow. I've made a build hook; with makeSetupHook which I'm putting in the stdenv's extraNativeBuildInputs. Loads of other packages build fine but not gmpxx. I can comment out preBuildHooks+=(something) or put it back, and this makes it pass/fail. The compiler detection fails unable to find libc. | 11:03:37 |
| p14 | Interestingly a develop shell reliably fails so I can't figure out why it's working in the working case. | 11:04:49 |
| p14 | I think I'm hitting a variant of https://github.com/NixOS/nixpkgs/issues/265121, that the buildPackages.stdenv.cc doesn't work as expected in a pkgsLLVM environment. | 11:05:35 |
| p14 | (because gmpxx uses this) | 11:05:45 |
| p14 | Right, figured it out. My develop environment was failing because of contamination from a direnv environment causing the wrong targetOffset, which meant I was trying to debug the wrong thing. And the preBuildHook was actually affecting the configure phase but later. | 11:55:47 |
| p14 | * Right, figured it out. My develop environment was failing because of contamination from a direnv environment causing the wrong targetOffset, which meant I was trying to debug the wrong thing. And the preBuildHook was actually affecting the configure phase but later; owing to how it affected the inputs to the derivation. | 11:56:01 |
| 21 Feb 2025 |
 Tristan Ross | I'm kinda wondering if it's possible to do "cross" things without activating the cross logic that causes the prefix/suffix to be added in. If it could be done with toolchain stuff and CPU model stuff, that'd be nice. For toolchains, we'll probably need multiple bootstrap tarballs. A base and then one for each toolchain. | 16:39:58 |
| 22 Feb 2025 |
| p14 | I totally want that and don't think there is a way. Even more, I'd love a way to be able to customize the tags that end up on package names, so we have more than just the -static marker. I totally think there should be an overridable function on the stdenv for controlling the markers. | 07:48:38 |
| p14 | * I totally want that and don't think there is a way. Even more, I'd love a way to be able to customize the tags that end up on package names, so we have more than just the -static marker. I think there should be an overridable function on the stdenv for controlling the markers. | 07:48:47 |
| p14 | * I totally want that and don't think there is a way. Even more, I'd love a way to be able to customize the tags that end up on package names, so we have more than just the -static marker. I think it would be awesome to have an overridable function on the stdenv for controlling the markers. | 07:49:00 |
| p14 | * I totally want that and don't think there is a way. It's currently keyed off stdenv.buildPlatform != stdenv.hostPlatform. Even more, I'd love a way to be able to customize the tags that end up on package names, so we have more than just the -static marker. I think it would be awesome to have an overridable function on the stdenv for controlling the markers. | 07:51:55 |
 @trofi:matrix.org | I wonder how cross-packages get their prefix. Maybe via stdenv.mkDerivation override? | 14:18:09 |
 Artturin | In reply to @trofi:matrix.org
I wonder how cross-packages get their prefix. Maybe via stdenv.mkDerivation override? Suffix https://github.com/NixOS/nixpkgs/blob/d91510fa191473465fd66e61f1cd4a1f838ee649/pkgs/stdenv/generic/make-derivation.nix#L382
Compiler prefix https://github.com/NixOS/nixpkgs/blob/d91510fa191473465fd66e61f1cd4a1f838ee649/pkgs/build-support/cc-wrapper/default.nix#L99 | 14:32:34 |
| 23 Feb 2025 |
| Tristan Ross | Yeah, I think we can slowly move there with equals vs like a isNative function. | 02:03:14 |
| Tristan Ross | I know there's canExecute but I think that's more of emulated included | 02:03:43 |
| Tristan Ross | So isNative would check more of whether the platforms are truly binary compatible | 02:04:20 |
 emily | no, hasEmulator is distinct from canExecute | 02:15:42 |
| Tristan Ross | I didn't know hasEmulator exists and I didn't bring it up. | 02:18:25 |
| emily | canExecute doesn't include emulators | 02:33:34 |
| emily | it's purely for e.g. i686 / x86_64 | 02:33:45 |
| emily | (also it's emulatorAvailable actually, whoops) | 02:34:09 |
| 26 Feb 2025 |
|  lzcunt changed their display name from sananatheskenana to lzcunt. | 18:20:36 |
| 7 Mar 2025 |
|  Qyriad changed their display name from Qyriad to qyriad. | 16:36:03 |
| 8 Mar 2025 |
| Qyriad changed their display name from qyriad to Qyriad. | 21:41:03 |
| 9 Mar 2025 |
 aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | I just got some really confusing differences in bash output between linux and darwin | 12:46:16 |
| aleksana 🏳️⚧️ (force me to bed after 18:00 UTC) | bash-5.2$ bash --version
GNU bash, version 5.2.37(1)-release (aarch64-apple-darwin24.3.0)
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
bash-5.2$ re='\bx\b'; [[ "x" =~ $re ]] && echo "yes!" || echo "no!"
no!
| 12:46:41 |
