 | Nix on macOS | 1135 Members |
| “There are still many issues with the Darwin platform but most of it is quite usable.” — http://yves.gnu-darwin.org | 180 Servers |
| Nix on macOS | 1135 Members |
| “There are still many issues with the Darwin platform but most of it is quite usable.” — http://yves.gnu-darwin.org | 180 Servers |
| Sender | Message | Time |
|---|---|---|
| 29 Oct 2025 | ||
 emily | it seems like we only ever do | 18:43:10 |
| emily | and | 18:43:11 |
| emily | | 18:43:12 |
| emily | I think we need to add apple-sdk to extraNativeBuildInputs in the native Darwin stdenv – then the cross one will pick it up. | 18:43:29 |
| 30 Oct 2025 | ||
 niklaskorz | Wil give that a try later today, thanks for the pointer! | 07:57:45 |
| niklaskorz | * Will give that a try later today, thanks for the pointer! | 08:26:07 |
| 31 Oct 2025 | ||
 mio | I am trying to build a qt6 package on darwin https://github.com/mio-19/nurpkgs/blob/7765bec6509aff3381493b1ddf73e4d74ded02cd/default.nix#L140 I got many "introduced in macOS 10.15" error In file included from /nix/store/d8kjnv6jj7hh4qrmr5bghs6jqm259gb2-qtbase-6.10.0/lib/QtCore.framework/Headers/QFile:1: /nix/store/d8kjnv6jj7hh4qrmr5bghs6jqm259gb2-qtbase-6.10.0/lib/QtCore.framework/Headers/qfile.h:66:22: error: 'native' is unavailable: introduced in macOS 10.15 66 | return View(path.native()).toString(); | ^ /nix/store/245wgmjlkq2swfkb138xh1jvb41ag8mh-libcxx-19.1.2+apple-sdk-15.5/include/c++/v1/__filesystem/path.h:670:44: note: 'native' has been explicitly marked unavailable here 670 | _LIBCPP_HIDE_FROM_ABI const string_type& native() const noexcept { return __pn_; } | ^ In file included from <built-in>:1: In file included from /nix/var/nix/builds/nix-48482-3499954108/source/build/src/framework/global/CMakeFiles/muse_global.dir/cmake_pch.hxx:5: In file included from /nix/var/nix/builds/nix-48482-3499954108/source/buildscripts/pch/pch.h:79: In file included from /nix/store/d8kjnv6jj7hh4qrmr5bghs6jqm259gb2-qtbase-6.10.0/lib/QtCore.framework/Headers/QFile:1: /nix/store/d8kjnv6jj7hh4qrmr5bghs6jqm259gb2-qtbase-6.10.0/lib/QtCore.framework/Headers/qfile.h:69:25: error: 'path' is unavailable: introduced in macOS 10.15 69 | inline std::filesystem::path toFilesystemPath(const QString &path) | ^ /nix/store/245wgmjlkq2swfkb138xh1jvb41ag8mh-libcxx-19.1.2+apple-sdk-15.5/include/c++/v1/__filesystem/path.h:382:33: note: 'path' has been explicitly marked unavailable here 382 | class _LIBCPP_EXPORTED_FROM_ABI path { | ^ In file included from <built-in>:1: | 01:06:01 |
| mio | * I am trying to build a qt6 package on darwin https://github.com/mio-19/nurpkgs/blob/7765bec6509aff3381493b1ddf73e4d74ded02cd/default.nix#L140 I got many "introduced in macOS 10.15" error | 01:06:14 |
| mio | * I am trying to build a qt6 package on darwin https://github.com/mio-19/nurpkgs/blob/7765bec6509aff3381493b1ddf73e4d74ded02cd/default.nix#L140 I got many "introduced in macOS 10.15" error | 01:06:22 |
| mio | I will try "-DCMAKE_OSX_DEPLOYMENT_TARGET=${stdenv.hostPlatform.darwinSdkVersion}" https://github.com/NixOS/nixpkgs/blob/d9376b2b549e33e71553901d7678461193f4d163/pkgs/by-name/wa/wamr/package.nix#L25 | 01:07:32 |
 samasaur | huh | 01:07:55 |
| samasaur | I wonder why CMake (apparently) doesn't pick up the min version properly from the stdenv | 01:10:27 |
| emily | it sounds like the project might be setting a deployment target in its own CMake files | 01:12:45 |
| mio | yes. I found it in cmake files | 01:14:19 |
| emily | might want to try just patching out that line | 01:14:33 |
| mio |  Download CleanShot 2025-10-31 at 12.31.53@2x.png | 01:32:02 |
| mio | I noticed that gtk packages like trayscale cannot find icons | 01:32:03 |
| mio |  Download CleanShot 2025-10-31 at 12.32.19@2x.png | 01:32:32 |
| mio | gnome-test-editor | 01:32:33 |
 saige leah changed their profile picture. | 07:11:33 | |
 twistedttea changed their display name from bartholomew to twistedttea. | 10:08:26 | |
| niklaskorz | so that wasn't it | 13:05:42 |
| niklaskorz | but I have a theory | 13:05:46 |
| niklaskorz | apparently cross compiling Rust crates that try to compile vendored C code are using the wrong compiler | 13:06:17 |
| niklaskorz | no that's not it, minimal reproducer using the cc crate correctly uses x86_64-unknown-linux-gnu-gcc | 13:25:03 |
| niklaskorz | but it's sufficient to add the liblzma-sys crate to a minimal application to reproduce | 13:29:44 |
| niklaskorz | * but it's sufficient to add the liblzma-sys crate to a minimal application to reproduce the linker failure | 13:30:15 |
 Randy Eckenrode | Is that crate doing something wrong in its build.rs that breaks with cross-compilation? | 13:30:24 |
| Randy Eckenrode | * Is that crate doing something in its build.rs that breaks with cross-compilation? | 13:30:33 |
| niklaskorz | I'm trying to find out, I suspect so | 13:30:46 |