| 29 Jan 2026 |
eveeifyeve | Known issue: https://github.com/NixOS/nix/issues/11676 | 10:38:24 |
eveeifyeve | * That is a known issue. | 10:39:08 |
eveeifyeve | * That is a known issue, no fix unfortantly. | 10:39:16 |
eveeifyeve | Also what is the solution for multiple installations on nix-darwin where it installs a separate nix. | 10:45:36 |
eveeifyeve | * Also what is the solution for multiple installations on nix-darwin where it installs a separate nix? | 10:45:42 |
eveeifyeve | * Also what is the solution for multiple installations on nix-darwin, where it installs a separate nix? | 10:45:50 |
eveeifyeve | Because at the moment I have one that is really old that I want to remove.
[FAIL] Multiple versions of nix found in PATH:
"/nix/store/6dw415pr1q4h1lywp3y0z6zij7h9wrsf-nix-2.31.2/bin"
"/nix/store/c20m7jl3x7a951sakyyfwngaxvlw7s63-nix-2.28.3/bin"
| 10:48:35 |
eveeifyeve | * Because at the moment I have one that is really old that I want to remove, which is used by default.
[FAIL] Multiple versions of nix found in PATH:
"/nix/store/6dw415pr1q4h1lywp3y0z6zij7h9wrsf-nix-2.31.2/bin"
"/nix/store/c20m7jl3x7a951sakyyfwngaxvlw7s63-nix-2.28.3/bin"
| 10:49:21 |
eveeifyeve | Nvm this is a quick and really easy fix. | 10:58:48 |
Randy Eckenrode | My branch uses staging as a base, so it (almost always) does a full bootstrap from source. | 11:35:26 |
Randy Eckenrode | sudo -i nix-env -e nix IIRC. | 11:36:26 |
Randy Eckenrode | Usually the Nix from the installer is left in root’s profile, but you don’t need it if your Nix is managed by nix-darwin. | 11:37:06 |
eveeifyeve | Yeah so I removed it.. | 11:37:23 |
eveeifyeve | Nix-darwin should create a first install script that uninstalls the one from the installer. | 11:38:16 |
eveeifyeve | We ❤️ llvm taking the longest to build in staging.... | 11:46:02 |
eveeifyeve | * We ❤️ llvm taking the longest to build in staging.... 😆 | 11:46:11 |
eveeifyeve | Randy Eckenrode: You were right I feel it does take 11 hours. I am at 6 hours and it's not built yet. | 13:14:57 |
eveeifyeve | It's hit to the point of the swift-cxx-bootrap (buildphase) | 13:15:18 |
eveeifyeve | Don't recommend anyone trying to build swift 6, but I am because I want to help out Randy Eckenrode. | 13:36:22 |
Randy Eckenrode | The biggest help will be testing. Try building packaged Swift applications as well as ones in a dev shell. It should work. The goal is to make it a good experience for packaging and for local development. | 13:43:13 |
Randy Eckenrode | If there are packages that need things that have been drops, I want to know, so I can investigate why. | 13:43:37 |
Randy Eckenrode | For example, swift.swift is gone. Were you just doing that to get an unwrapped compiler? | 13:44:07 |
Randy Eckenrode | The compiler is now unwrapped. | 13:44:29 |
Randy Eckenrode | Using xcbuild with Swift dependencies? I want to make that work. | 13:45:21 |
Randy Eckenrode | Using NIX_SWIFTFLAGS_COMPILE? It’s no longer supported due to Swift being unwrapped. How was that being used? | 13:46:15 |
Randy Eckenrode | Need to link non-Swift dylibs? Does that still work? | 13:46:35 |
Randy Eckenrode | If there are easy test cases, they can be put in passthru.tests. I’ve already updated the C++ interop test for both-way interop. | 13:47:30 |
Randy Eckenrode | We can now use Swift from C++ in addition to C++ from Swift. | 13:48:02 |
Randy Eckenrode | Other bonus things I hope will work is cross-compilation and using stdlibs for other targets. | 13:48:37 |
Randy Eckenrode | Static is another one that needs testing. | 13:49:48 |