| 18 Jan 2026 |
 Randy Eckenrode | We ran into it with something else last year. | 20:27:34 |
|  isabel changed their profile picture. | 20:43:37 |
| 19 Jan 2026 |
| Randy Eckenrode | https://bugs.gentoo.org/950943 | 00:23:02 |
| Randy Eckenrode | I tried to reproduce the failure interactively, but I failed. The Gentoo bug report suggests it doesn’t happen every time. | 00:48:23 |
| Randy Eckenrode | Those are always fun to debug. | 00:48:32 |
| Randy Eckenrode | I kept restarting the build. It eventually built. 🤪 | 01:11:51 |
|  Jeanre Swanepoel joined the room. | 07:22:07 |
| Jeanre Swanepoel | morning all, I am redoing my nix config, but I am thinking about system packages vs home-manager packages | 07:22:35 |
|  bl1nk changed their profile picture. | 10:39:33 |
| Randy Eckenrode | Maybe need to use sudo not to use the daemon? 😬 | 17:24:35 |
| Randy Eckenrode | Moving the Swift discussion back to here. It’s not clear why the cc-wrapper changes would be an issue on Linux but not Darwin. Is it something to do with how Swift is vendoring its own custom copy? | 20:10:09 |
| Randy Eckenrode | I’m not exactly sure what to do about the libstdc++ breakage though. That’s going to block any work on Linux support even if I don’t use GCC to build Swift on Linux. | 20:10:58 |
 Katalin 🔪 | what's the libstdc++ breakage? | 20:11:31 |
 samasaur | https://github.com/NixOS/nixpkgs/pull/468796 | 20:12:40 |
| Katalin 🔪 | ah, this is 5.10 | 20:13:40 |
| Katalin 🔪 | could always build it with its libc++ or against compatible mainline libc++ :^) | 20:14:44 |
| samasaur | yeah | 20:14:45 |
| samasaur | * yeah (to 5.10) | 20:15:27 |
| Katalin 🔪 | though ime that's sorta broken on 5.10, or at least I didn't get it to work when I built 5.10 for bootstrapping 6.x on gentoo | 20:15:30 |
| samasaur | the new issue is that 5.10 is failing on darwin now with a crash in the bootstrapped swiftc | 20:16:13 |
| samasaur | on staging-next | 20:16:27 |
| Randy Eckenrode | I think libstdc++ is the intended C++ stdlib on Linux. If we built against libc++, we couldn’t interop with anything in the default package set. | 20:16:40 |
| Randy Eckenrode | Swift can’t target multiple C++ implementations for interop. You have to pick one when building the compiler. | 20:17:32 |
| Katalin 🔪 | yeah', that's true. I thought about having a swiftStdenv of some kind which would select the correct compiler/STL but you would still have to compile packages you wanted to use from swift with that. so yeah. not ideal. scratch that | 20:19:12 |
| Randy Eckenrode | Given that Swift is broken upstream by GCC 15, I may just land working Darwin support with enough Linux to get to the point of failing. | 20:19:18 |
| Randy Eckenrode | That’s how it is today (but for other reasons). | 20:20:04 |
| Randy Eckenrode | I do provide a swiftPackages.stdenv in the rewrite, but it’s just a clangStdenv because I’m not even wasting my time building with GCC. | 20:20:28 |
| samasaur | that would be great (from my end at least), given that the existing upstream 5.10 is in maintenance mode only so to speak | 20:20:56 |
| Randy Eckenrode | I could also make Swift propagate Clang and support regular stdenvs. I’m not super thrilled about that, but it would avoid misuse. | 20:21:02 |
| Katalin 🔪 | yeah, and for bidirectional interop you do need clang anyway | 20:21:06 |
