Nixpkgs Stdenv | 258 Members | |
| 80 Servers |
| Sender | Message | Time |
|---|---|---|
| 14 Sep 2023 | ||
| Will cross-post here for general amusement as well: Fun fact: | 22:14:07 | |
| 15 Sep 2023 | ||
In reply to @trofi:matrix.orgCould it cause https://github.com/NixOS/nixpkgs/issues/41340 | 01:19:42 | |
| * In reply to @trofi:matrix.org Will cross-post here for general amusement as well: Fun fact: nix has headers-only nlohmann_json dependency in it's output closure and pipewire has python. Chances are https://github.com/NixOS/nixpkgs/pull/255192 will fix it (more words: https://trofi.github.io/posts/298-unexpected-runtime-dependencies-in-nixpkgs.html). Could it cause https://github.com/NixOS/nixpkgs/issues/41340 on large closures | 01:20:41 | |
| * Could it cause https://github.com/NixOS/nixpkgs/issues/41340 on large closures | 01:21:03 | |
| Yup. I initially tried without deduping the argument and got failures on `qemu`. I'm sure it also makes the process forking slower. Would be nice if `nixpkgs` used response files for all of it`s unbounded argument lists :) | 05:46:22 | |
| 16 Sep 2023 | ||
| I've got a pipeline of things I want to fix to make pkgsLLVM.pkgsStatic to work well, but review is going slow. I don't want to generate a mass of PRs which go unreviewed for a long time since that risks increasing the infinite TODO list for everybody. Any kind souls able to help me clear this review from the pipeline? I hope it is uncontroversial. https://github.com/NixOS/nixpkgs/pull/253116 | 09:07:47 | |
| * [xpost from exotic nix targets] I've got a pipeline of things I want to fix to make pkgsLLVM.pkgsStatic to work well, but review is going slow. I don't want to generate a mass of PRs which go unreviewed for a long time since that risks increasing the infinite TODO list for everybody. Any kind souls able to help me clear this review from the pipeline? I hope it is uncontroversial. https://github.com/NixOS/nixpkgs/pull/253116 | 09:08:01 | |
| 12:38:24 | ||
| stdenv/patch-shebangs fix: https://github.com/NixOS/nixpkgs/pull/255463 | 14:53:23 | |
| 20 Sep 2023 | ||
Quiz Question: how many arguments to a binary do you think you can pass as a maximum on Linux? :) (directly related to cc-wrapper abusing NIX_CFLAGS_COMPILE and friends). | 20:56:26 | |
| 21 Sep 2023 | ||
| Spoilers (not a lot): https://trofi.github.io/posts/299-maximum-argument-count-on-linux-and-in-gcc.html | 18:38:01 | |
| 23:09:44 | ||
| 24 Sep 2023 | ||
In reply to @trofi:matrix.orgI ran into similar issues when building Firefox and telegram desktop with musl libc | 14:46:32 | |
| execve would fail because the environment was too large | 14:46:49 | |
| I vaguely remember musl decided to do 128K long stacks (or similar). | 14:47:53 | |
| Yeah, because that is also the max env size defined in Linux kernel headers | 14:48:31 | |
| * Yeah, but also 128K or so is the max env size defined in Linux kernel headers | 14:48:57 | |
| For compatibility reasons or something | 14:49:15 | |
| Yeah, it's an arbitrary limit. Would be nice to increase it to 6M :) | 15:07:33 | |
In reply to @yuka:yuka.devper variable that is | 15:25:41 | |
| a different maximum applies to the env as a whole, according to the article i think? | 15:26:16 | |
In reply to @trofi:matrix.orgbetter do it soon so we can use it in 3 years 😅 | 15:30:25 | |
| I saw news about the lts kernels moving to 2 years of support | 15:34:21 | |
| Let's try https://lkml.org/lkml/2023/9/24/381 :) | 19:30:52 | |
| good see you in 6.7 | 20:10:32 | |
| backport 😄 (i don't know how kernel backports work) | 20:12:52 | |
| won't happen | 20:13:11 | |
NixOS can always do it without the upstream blessing :) | 20:15:54 | |
| (but I don't think it's a good idea) | 20:16:13 | |
In reply to @trofi:matrix.orgyeah but we would drop support for all other distros | 20:16:13 | |