| 26 Feb 2026 |
 Tristan Ross | https://github.com/NixOS/nixpkgs/pull/494215 I have a fix | 02:15:22 |
|  Lily Foster changed their profile picture. | 14:01:23 |
 crazychaoz | alright, that fixed it
but why does it have to be fixed?!?
i am specifically cross compiling to windows (my usage of pkgsCross.mingwW64), and i want to compile stuff that is only for windows (windows specific pthread stuff), so why do i have to specify the designation of this package is for windows?
also why was that changed (it worked before)?
| 14:24:41 |
 K900 | windows is a general namespace for Windows specific packages | 14:25:46 |
| K900 | There's no pthreads package at top level because it's normally provided by libc | 14:25:54 |
| crazychaoz | obviously, but i am compiling with pkgsCross.mingwW64.stdenv, why do i have to give additional information as to where the windows specific headers should end up at?
i have had issues before with tools that need to get compiled on host&target (eg. protobuf) but here the situation should be clear? i run compilation for windows, with win pthreads, why would i ever want to compile windows.pthreads for non windows targets?
| 14:32:30 |
| K900 | Look, that's just how nixpkgs is structured | 14:34:43 |
| crazychaoz | ack | 14:38:01 |
 rosssmyth | I would like to fix it, but testing and implementing cross is annoying due to different people telling me different things of what to do and what not to do. | 15:42:06 |
| rosssmyth | * I would like to fix it, but testing and implementing it is annoying due to different people telling me different things of what to do and what not to do. | 15:42:13 |
 Artturin | pthreads should be in buildInputs | 15:44:00 |
| Artturin | The reason it works for you is that you're not using a cross stdenv so strictDeps isn't enabled | 15:44:19 |
| Artturin | * The reason nativeBuildInputs works for you is that you're not using a cross stdenv so strictDeps isn't enabled | 15:44:35 |
| Artturin | pkgsCross.mingwW64.windows.pthreads you can put this in buildInputs and it won't need pkgsHostTarget | 15:47:15 |
| Artturin | * pkgsCross.mingwW64.windows.pthreads you can put this in buildInputs and it won't need a explciit pkgsHostTarget | 15:47:26 |
| Artturin | * pkgsCross.mingwW64.windows.pthreads you can put this in buildInputs and it won't need a explicit pkgsHostTarget | 15:47:38 |
|  Aoinoikaz joined the room. | 15:48:41 |
 dramforever | oh, i missed that completely and was wondering why you need it in depsBuildBuild | 19:38:52 |
| dramforever | depsBuildBuild is what's making it select a x86_64-linux windows.pthreads | 19:39:40 |
| dramforever | (which does not exist) | 19:39:45 |
| dramforever | it working before was the broken state, where depsBuildBuild has failed to select the x86_64-linux one | 19:42:51 |
| dramforever | oh wait i probably misunderstood | 19:46:42 |
| dramforever | do you mean you were using pkgsCross.mingwW64.stdenv.mkDerivation? that would do the right thing wrt dependencies | 19:47:14 |
| dramforever | if you were just adding pkgsCross.mingwW64.stdenv.cc it wouldn't change the fact that you have a native x86_64-linux stdenv | 19:47:56 |
| Artturin | https://github.com/CrazyChaoz/backtor/blob/c9552af05f426dc3faff29b4efc6b0100e08699a/flake.nix#L40 | 19:51:41 |
| Artturin | This should really be true so you can be sure that you have the right behaviour | 19:51:55 |
| dramforever | i can't tell if this crane thing is doing the right thing | 19:53:08 |
| rosssmyth | If you are using Crane, if you use pkgsCross.mingwW64.callPackage, you do not have to manually specify windows.pthreads | 19:54:18 |
| rosssmyth | Because of a change a really cool person did
https://github.com/ipetkov/crane/commit/7cc51a10ddafa9ed1693afdf26d1bffb6ce027a0 | 19:55:13 |
| dramforever | ... i fail to see how | 19:55:19 |
