Nixpkgs Stdenv | 265 Members | |
| 82 Servers |
| Sender | Message | Time |
|---|---|---|
| 11 Aug 2023 | ||
| cp itself also prints "invalid argument" and returns nonzero | 16:17:47 | |
| ah, this was caused by the coreutils 9.3 upgrade likely | 16:21:15 | |
| that's kind of awkard... | 16:23:21 | |
| 13 Aug 2023 | ||
| 01:27:28 | ||
| 15 Aug 2023 | ||
| 14:57:25 | ||
| 19:34:39 | ||
| 17 Aug 2023 | ||
| 11:57:33 | ||
| 22 Aug 2023 | ||
| 13:06:48 | ||
| 27 Aug 2023 | ||
| 22:08:35 | ||
| 29 Aug 2023 | ||
| https://github.com/NixOS/nixpkgs/pull/251853 | 19:05:05 | |
| 3 Sep 2023 | ||
| I would like to address https://github.com/NixOS/nixpkgs/issues/111010#issuecomment-1536424163 but it will require changing the cc-wrapper. [fix is to account for Anyone see any problems with doing so, or any suggestions on implementation, can I submit a fix to staging? | 09:45:32 | |
| One way to find out if it gives problems, go for it | 10:49:15 | |
| Doing a local build with an obvious fix before I send it, let's see how that pans out. | 10:49:39 | |
In case anyone has suggestions/criticisms. I should have a build of some nontrivial software within an hour or two. | 10:50:55 | |
Darn, that doesn't seem to be right. Should I be putting NIX_CFLAGS_LINK there rather than NIX_CFLAGS_LINK_@suffixSalt@, or possibly even both? | 11:03:19 | |
| I guess that's also not right because we don't want to inject the link flags into the params so early anyway (even if it might be nice to have the CFLAGS_LINK response-expanded... | 11:06:46 | |
| Candidate fix. I've been able to build/run pkgsStatic.pkgsLLVM.hello using this (on staging, also using LLVM 16) https://github.com/NixOS/nixpkgs/pull/253116 | 12:54:32 | |
Artturin: I also tried building pkgsStatic.pkgsLLVM.clang.cc -- for this I hit the error message you described in https://github.com/NixOS/nixpkgs/issues/22060 ( file RPATH_CHANGE could not write new RPATH:) while installing llvm. | 12:55:49 | |
* Artturin: I also tried building pkgsStatic.pkgsLLVM.clang.cc -- for this I hit the error message you described in https://github.com/NixOS/nixpkgs/issues/22060 ( file RPATH_CHANGE could not write new RPATH:) while in the ninja install phase of llvm. | 12:56:00 | |
| Is there any testing machinery someone can run #253116 through, is it possible to have a hydra job for it? | 12:57:51 | |
Running nix build -f tests.cc-wrapper | 13:07:16 | |
| * Im running nix build -f tests.cc-wrapper | 13:07:48 | |
| * Im running `nix build -f tests.cc-wrapper` | 13:07:59 | |
| it built | 14:28:22 | |
| Artturin: What next? Any opinion as to whether it may go into staging? | 14:31:08 | |
In reply to @p14:matrix.orgFor this it seems I want to set -DCMAKE_SKIP_INSTALL_RPATH=On to avoid the cmake error. Would it make sense to inhibit this in general with the static build stdenv adaptor? | 15:29:31 | |
Hmm, it's not clear where to put such logic. Essentially "if we're building static binaries, we don't have an rpath and we don't want cmake to do rpath manipulation". Feels like it could go into makeStaticBinaries. | 15:37:36 | |
| Success, I was able to build pkgsStatic.pkgsLLVM.clang.cc, and it also appears to work. | 15:58:26 | |
| Needed this to fix cmake builds though, does it seem reasonable?
| 15:59:30 | |
In reply to @p14:matrix.orgsuperficially ok but put it in a separate PR | 16:11:25 | |