| 25 Feb 2026 |
 rosssmyth | makes sense | 15:26:31 |
 Artturin | So actually now that pkgs is spliced the issue is that they're spliced now :D | 15:27:31 |
| Artturin | To not splice you need to be explicit pkgsCross.mingwW64.pkgsBuildHost.windows.pthreads. This will get rid of the error | 15:28:57 |
 crazychaoz | it did not get rid of my error sadly, could anybody test my build please? | 16:00:10 |
 dramforever | pkgsCross.mingwW64.pkgsHostTarget.windows.pthreads | 16:05:08 |
| dramforever | HT is the normal one, BH is buildPackages, BB is buildPackages.buildPackages | 16:07:04 |
| dramforever | the rest are cursed | 16:07:08 |
| 26 Feb 2026 |
 Tristan Ross | pkgsLLVM.freetype fails huh
libtool: compile: aarch64-unknown-linux-gnu-clang -pedantic -std=c99 -I/build/freetype-2.13.3/src/base -I/build/freetype-2.13.3/objs -I./builds/unix -I/build/freetype-2.13.3/include -c -Wall -fvisibility=hidden -I/nix/store/kf8y80j08xard2g6ly6kiv95irxh3k0d-zlib-aarch64-unknown-linux-gnu-1.3.1-dev/include -I/nix/store/86f3r04x20hacjjalkkh9025ysndi667-bzip2-aarch64-unknown-linux-gnu-1.0.8-dev/include -I/nix/store/asar6vn00qxkahs2xhwiw7srnrf5nahm-libpng-apng-aarch64-unknown-linux-gnu-1.6.55-dev/include/libpng16 -I/nix/store/r42r691764ajdchf9fzgmxvqdlwgds83-brotli-aarch64-unknown-linux-gnu-1.2.0-dev/include -pthread "-DFT_CONFIG_CONFIG_H=<ftconfig.h>" "-DFT_CONFIG_MODULES_H=<ftmodule.h>" "-DFT_CONFIG_OPTIONS_H=<ftoption.h>" -DFT2_BUILD_LIBRARY /build/freetype-2.13.3/src/base/fttype1.c -o /build/freetype-2.13.3/objs/fttype1.o >/dev/null 2>&1
/build/freetype-2.13.3/src/base/ftver.rc:19:9: fatal error: 'windows.h' file not found
19 | #include<windows.h>
| ^~~~~~~~~~~
1 error generated.
| 01:45:51 |
| Tristan Ross | Wait, is it because RC=aarch64-unknown-linux-gnu-windres... | 02:05:24 |
| Tristan Ross | Oh no, unsetting it fixes the issue | 02:06:08 |
| Tristan Ross | https://github.com/NixOS/nixpkgs/pull/482391 might've caused it | 02:08:45 |
| 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 |
