| 14 Jul 2025 |
 John Ericson | I would expect it to be hard to remove them | 20:32:29 |
 lzcunt | Hey there, I'm trying to build for freestanding loongarch64, however it seems like we default on "newlib" as the libc for both "-none" and "-elf" but newlib doesn't support loongarch64. | 20:54:04 |
 Artturin | Tried specifying libc = "something";? | 20:55:31 |
| Artturin | * Tried specifying libc = "something"; in the platform config? | 20:55:43 |
| lzcunt | yea ofc that works but it's awkward that -none means newlib especially for architectures that newlib doesn't support | 20:56:05 |
| Artturin | https://github.com/NixOS/nixpkgs/blob/0455292066a49d3670dd7709ee82deb5531aa3c4/lib/systems/default.nix#L152 | 20:56:28 |
| lzcunt | should nixpkgs maybe not default to newlib for those architectures? | 20:57:59 |
| lzcunt | ok so this doesn't work | 21:06:43 |
| Artturin | In what way? | 21:07:32 |
| Artturin | In the way that it doesn't override the libc selection in systems/default.nix? | 21:07:47 |
| Artturin | Or just a build issue | 21:07:53 |
| lzcunt | I'm trying to get a blame 1 minute | 21:13:12 |
| lzcunt | https://github.com/NixOS/nixpkgs/blob/0455292066a49d3670dd7709ee82deb5531aa3c4/pkgs/top-level/all-packages.nix#L8188 this wasn't updated in 5c1955ff1404eddf3c0379a0573aabe83ac5bca3 (libcCross: Remove!) | 21:21:31 |
| lzcunt | but even if it was, setting anything other than null would throw | 21:21:51 |
| lzcunt | and gcc can't target something with libc = null; because it uses the libc name in the include dir path | 21:24:20 |
| lzcunt | basically in several places nixpkgs pretty much requires newlib for freestanding targets | 21:25:17 |
