 | Nix on macOS | 1146 Members |
| “There are still many issues with the Darwin platform but most of it is quite usable.” — http://yves.gnu-darwin.org | 181 Servers |
| Nix on macOS | 1146 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 |
|---|---|---|
| 25 Nov 2025 | ||
 Randy Eckenrode | It had to be ported to the clang-tools wrapper, which would have gone to master if not for the large number of Linux rebuilds it caused. | 11:34:43 |
 megmug | Aha - could this possibly affect non-module projects as well then? Because I am still getting errors despite removing all the modules. clang-scan-deps fails to find some stuff (on macos). | 11:37:28 |
| Randy Eckenrode | If it uses clang-scan-deps, it will be broken. | 11:39:02 |
| Randy Eckenrode | Also clangd. | 11:39:10 |
| Randy Eckenrode | You may be able to work around it by setting env.NIX_CFLAGS_COMPILE to -isystem ${stdenv.cc.libcxx}. | 11:42:42 |
| Randy Eckenrode | * You may be able to work around it by setting env.NIX_CFLAGS_COMPILE to -isystem ${stdenv.cc.libcxx}/include/c++/v1. | 11:43:01 |
| Randy Eckenrode | (Path from memory, so may be off.) | 11:43:14 |
| megmug | Hm, or just build the nix-shell on a different version maybe? Is the change already on master branch? Or can i go back far enough to get a version that didn't have the problem? | 11:44:38 |
| Randy Eckenrode | It’s on staging. It won’t make it to master until mid-December probably. | 11:47:04 |
| Randy Eckenrode | If you use staging, you’ll have to do a stdenv bootstrap and build everything from source. | 11:47:43 |
| megmug | Do I understand correctly that the breaking change was merged on oct 9? Could it be circumvented by going back further than that? | 11:52:20 |
| megmug | On the other hand, building everything from source might not be that bad as long as it's automatic | 11:53:09 |
| Randy Eckenrode | That should also work. | 11:56:55 |
| Randy Eckenrode | It is. It just takes a while. | 11:57:18 |
| megmug | After waiting for hours to let the machine build the staging commit, i had to discover that my issue persisted. After getting a message from a teammate that the project didn't build for him on an ubuntu Windows-WSL VM, i got suspicious. I thought i had double-checked with nix-shell --pure that it would build on other machines. And i was even using ubuntu for the test. It turns out we were missing a dependency. After adding pkgs.clang-tools into the nix-shell packages, the issue was resolved for the teammate and also on the Mac! I learned that it can be really difficult to make things work across different OSes and architectures. Without Nix it would without a doubt be a lot more difficult, though. | 22:41:44 |
| megmug | BTW, K900 , everything seems to work now including modules. Maybe our use case is simple enough for the existing system to handle it, but at least some amount of module support (using clang) is apparantly there now. | 22:48:33 |
| 26 Nov 2025 | ||
 Martin joined the room. | 19:19:47 | |
 Sarah Clark | Are there any plans to land the pyarrow fixes for Darwin any time soon? Pretty much any python package in the AI space depends on it and the Hydra failure numbers for Darwin are alarming. | 21:55:38 |
| Randy Eckenrode | The PRs referenced in https://github.com/NixOS/nixpkgs/issues/461396 are marked draft or closed. If they’re targeting staging, they probably won’t land until early/mid-December. I think the plan is to do one last staging-25.05 cycle before doing another staging cycle. | 22:03:59 |
| Sarah Clark | I hope so. I can't even run nixpkgs-review on Darwin for most of my PRs due to this not building. | 22:26:17 |
 niklaskorz | the correct PR is https://github.com/NixOS/nixpkgs/pull/426611 | 22:45:15 |
| niklaskorz | (if I understand correctly) | 22:45:20 |
| 27 Nov 2025 | ||
 mio | Does anyone know how to fix errors like this? https://github.com/NixOS/nixpkgs/pull/465340#issuecomment-3583946614 | 02:25:46 |
| Randy Eckenrode | Why is it copying all of the dylibs into the Frameworks folder? | 03:01:12 |
| Randy Eckenrode | * Why is it copying all of the dylibs into the Frameworks folder? | 03:01:20 |
| Randy Eckenrode | Oh, it’s qtmacdeploy. Is there a way to make it stop doing that? | 03:08:41 |
| Randy Eckenrode | * Oh, it’s macdeployqt . Is there a way to make it stop doing that? | 03:09:13 |
| Randy Eckenrode | mio, this patch appears to work for me. It doesn’t solve the mpvqt issue. The nixpkgs one builds, but https://gist.github.com/reckenrode/0f70490429733aacb0091a05deb1653b | 03:23:07 |
| Randy Eckenrode | I’m able to run it, but I can’t connect to my server because its certificates expired. For some reason, Let’s Encrypt won’t renew. I was in the process of upgrading my servers to 25.05 when I got sidetracked fixing a libcurl regression …. | 03:24:23 |
| mio | I applied your patch to pic/jellyfin-qt6 | 04:40:00 |