| 31 Dec 2024 |
 Maxim Moseychuk | If pkgsCross is another instance of nixpkgs, I tried passing it as an explicit parameter, and it worked.
# nix-build --arg pkgs "(import <nixpkgs> {}).pkgsCross.aarch64-multiplatform" -A myhello
| 09:33:26 |
|  getchoo changed their profile picture. | 12:38:42 |
|  siraben (he/him) left the room. | 14:51:15 |
| 1 Jan 2025 |
|  mjolnirchanged room power levels. | 14:26:28 |
|  @wegank:matrix.org left the room. | 20:00:23 |
|  jopejoe1 changed their display name from jopejoe1 [4094] to jopejoe1. | 23:29:54 |
| 2 Jan 2025 |
 rhelmot | alright chat I think we are almost out of dogshit edge cases before I can resume reviews on the rustc stuff | 09:09:31 |
| rhelmot | this last case comes from being on freebsd and compiling... get ready for it... | 09:09:45 |
| rhelmot | pkgsCross.aarch64-multiplatform.pkgsLLVM.buildPackages.rustc | 09:09:59 |
 K900 | One day we'll get to Qt6 cross | 09:10:15 |
| K900 | And then to KF6 | 09:10:17 |
| K900 | And then we'll have to figure out corrosion on cross | 09:10:23 |
| K900 | And I am not looking forward to that day | 09:10:28 |
| rhelmot | the problem for the thing I posted seems to be related to clang being multi-target now. we tell rustc configureFlags that --set=target.aarch64-unknown-linux-gnu.linker=/nix/store/6bjs7ai2ai14fdx6kvrfgdfhc16a19md-aarch64-unknown-linux-gnu-clang-wrapper-19.1.6/bin/aarch64-unknown-linux-gnu-clang which is correct but it doesn't pass any flags indicating what linker to use, so it just uses un-prefixed ld which is NOT multi-target and so the compile fails | 09:13:52 |
| rhelmot | ld is gnu binutils here | 09:14:44 |
| rhelmot | is this even a legal configuration? | 09:14:52 |
| rhelmot | I can't remember why I set up the freebsd stdenv to be clang + gnu binutils but it's been working until now... | 09:16:15 |
| 3 Jan 2025 |
|  elikoga changed their display name from elikoga (@38c3 📞488{0,1,9}) to elikoga. | 10:28:12 |
|  lzcunt joined the room. | 15:05:59 |
|  ghpzin joined the room. | 15:25:00 |
| lzcunt | and I've been stuck with this issue where the mlibc package that I'm working on has infinite recursion because it's build dependencies depend on the stdenv with mlibc instead of the mlibc for the build platform | 16:17:43 |
| lzcunt | * Hey there, I've been trying to add a new libc (mlibc) to nixpkgs and I've been stuck with this issue where the mlibc package that I'm working on has infinite recursion because it's build dependencies depend on the stdenv with mlibc instead of the mlibc for the build platform | 16:18:30 |
| lzcunt | I've been told you guys can maybe help with my issue | 16:18:54 |
| lzcunt | * Hey there, I've been trying to add a new libc (mlibc) to nixpkgs and I've been stuck with this issue where the mlibc package that I'm working on has infinite recursion because it's build dependencies depend on the stdenv with mlibc instead of the stdenv for the build platform | 16:19:27 |
 Artturin | Show the code | 16:19:34 |
| lzcunt | I have it in https://github.com/lunabunja/nixpkgs in the mlibc/init branch | 16:20:05 |
| lzcunt | you can see that nix-build . -A mlibc works (mlibc built with build=host=target=glibc or musl) but nix-build . -A pkgsCross.x86_64-linux-mlibc.hello does not work - it tries building mlibc with host=linux-mlibc and fails because it also tries building its dependencies in nativeBuildInputs (meson and ninja) with the mlibc stdenv | 16:23:52 |
| lzcunt | * you can see that nix-build . -A mlibc works (mlibc built with build=host=target=glibc or musl) but nix-build . -A pkgsCross.x86_64-linux-mlibc.hello does not work - it tries building mlibc with host=linux-mlibc and fails because it also tries building its dependencies in nativeBuildInputs (meson and ninja) with the mlibc stdenv (which hasn't been built yet so infinite recursion) | 16:24:30 |
| lzcunt | there's more details in #dev:nixos.org | 16:25:26 |
 Tristan Ross | It's probably an infinite recursion which the cc | 16:31:32 |
