Nixpkgs Stdenv | 221 Members | |
| 72 Servers |
| Sender | Message | Time |
|---|---|---|
| 7 Feb 2025 | ||
| 22:45:33 | ||
| 8 Feb 2025 | ||
| 02:24:25 | ||
| 02:24:59 | ||
| vcunat: do you remember what needed And I wonder if we should just drop | 16:20:31 | |
cmake hook also added it with DCMAKE_INSTALL_OLDINCLUDEDIR https://github.com/NixOS/nixpkgs/commit/c0d2f924590918b0176aaf1f84ccf372ce4f13c4 . I suspect just to follow stdenv. | 16:24:37 | |
| No, I don't recall at all. It's been a bit long :-) | 16:24:40 | |
| :) | 16:25:00 | |
| Proposed the removal as https://github.com/NixOS/nixpkgs/pull/380400 | 16:51:24 | |
| Also asked on #macos:nixos.org if it's used by any chance there (AFAIU it should not be load-bearing) | 16:53:25 | |
| 13 Feb 2025 | ||
| 06:59:21 | ||
| 15 Feb 2025 | ||
| 10:16:57 | ||
| 10:43:08 | ||
| 19 Feb 2025 | ||
| So should I just send https://github.com/NixOS/nixpkgs/pull/380325 | 09:51:10 | |
| (again) | 09:51:12 | |
| Probably yeah | 10:57:31 | |
| All right, let's see if it blows up this time | 11:05:21 | |
| 20 Feb 2025 | ||
| 09:58:16 | ||
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 | |
| Interestingly a develop shell reliably fails so I can't figure out why it's working in the working case. | 11:04:49 | |
| 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 | |
| (because gmpxx uses this) | 11:05:45 | |
| 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 | |
| * 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 | ||
| 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 | ||
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 | |
* 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 | |
* 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 | |
* 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 | |
I wonder how cross-packages get their prefix. Maybe via stdenv.mkDerivation override? | 14:18:09 | |
In reply to @trofi:matrix.org 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 | |