Nix on macOS | 1144 Members | |
| “There are still many issues with the Darwin platform but most of it is quite usable.” — http://yves.gnu-darwin.org | 181 Servers |
| Sender | Message | Time |
|---|---|---|
| 16 Nov 2025 | ||
| this person im talking to on discord says it broke by updating to 26.1 | 23:38:48 | |
| guess I'll hold out a bit longer on 15 | 23:45:35 | |
| 17 Nov 2025 | ||
| consistently hitting
This is on a machine that upgraded to 26.0.1. I cannot reproduce the same on another machine that is still on 15.6.1. (community builder which is on 15.7.2 is also fine.) May I ask someone with 26.x to rebuild it locally from upstream master and see if you by chance can hit the same issue too? btw what is the version running in Hydra? | 00:51:28 | |
oh my god :( | 00:55:43 | |
| I can hit the same issue on a --rebuild of gnugrep. | 00:56:35 | |
| hm. we could skip the test I guess but it probably tells us something important - that all projects using gnulib are better off backporting the fix? | 00:59:53 | |
| gonna upgrade the machine to 26.1 today and see if it's still an issue. | 01:02:07 | |
| Lun: which version are you on | 01:03:12 | |
| It’s not a bug. POSIX doesn’t require multithread safety. | 01:09:06 | |
| 26.1 | 01:09:22 | |
| This is also a known issue. I was complaining about it earlier today. I had thought someone would have submitted PRs to disable the tests. | 01:09:28 | |
| Does the patch fix the issue? I was using a workaround set of commits that just disabled the test. | 01:10:22 | |
| I see. where has the complaining happened? I checked the patch - it does some static array of a limited size carrying results over subsequent calls. looks like an actual fix.
| 01:12:34 | |
| https://matrix.to/#/!lheuhImcToQZYTQTuI:nixos.org/$lL5OOpX3h6xkj46aagLfnJGDZFA_4TxSysI7IyIqToU?via=nixos.org&via=matrix.org&via=nixos.dev | 01:12:59 | |
| I saw c-ares thingy. is it the same? | 01:13:40 | |
Why not check for __APPLE__ and error out for an unknown platform? | 01:13:42 | |
| oops nevermind, matrix client is misbehaving | 01:14:01 | |
| No. I ran into it trying to get Lix to use a fixed curl in my configs. I ended up doing this lovely override:
| 01:14:18 | |
| * No. I ran into it trying to get Lix to use a fixed curl in my configs. I ended up doing this lovely override:
| 01:14:39 | |
| guess I'll 1) post a staging patch backporting the gnulib fix for gnugrep; 2) report a bug to gnugrep so that they bump their gnulib submodule. (they are still sitting on an Apr 2025 commit in master) | 01:17:49 | |
| My configs were my Swift branch from July, so I had some work to do to update them. My servers are actually still on 24.11, which should be fun to update. | 01:17:59 | |
| It also affects coreutils. Probably anything using gnulib, but we don’t have a good way of dealing with that because we don’t de-vendor gnulib. | 01:18:24 | |
| Now that I have a working Lix again, I can try building KosmicKrisp. | 01:19:07 | |
| yep anyone using an old gnulib is affected. frankly, anyone NOT using gnulib is also affected. (if they use the interface) | 01:19:18 | |
| (if they use the interface AND assume it's safe) | 01:19:42 | |
| it's not clear if gnugrep is affected per se - I don't think it's multi-threaded? | 01:20:20 | |
| they just run all tests from gnulib regardless. | 01:20:33 | |
| the patch implementing MT for grep is 10 yo and not merged: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20768 so probably it's enough to disable the test after all | 01:26:10 | |
| Requires Metal 4. Good thing we have the 26.0 SDK. | 01:28:19 | |
| KosmicKrisp doesn’t appear to be included in Mesa 25.3. | 01:31:37 | |