| 29 Jun 2025 |
 K900 | But if you want an LLVM built kernel, you're on your own right now really | 17:04:41 |
| K900 | We don't support that configuration | 17:04:47 |
 Electro | Oof | 17:04:59 |
 Tristan Ross | I have a fix, just waiting review lol | 17:05:13 |
| Electro | It's broken? | 17:05:24 |
| Tristan Ross | Yes, it pulls in GCC instead | 17:05:35 |
| Tristan Ross | But the PR properly pulls in clang | 17:05:48 |
| K900 | It's unsupported, which means it's not something we test or generally care about | 17:05:48 |
| Tristan Ross | Tbf, I have been working on fixing pkgsLLVM to work better. | 17:08:21 |
| Electro | Is there a reason the wrapped clang adds --target automatically? Isn't clang supposed to be a cross-compiler? Some constraint from working with nix? | 17:10:14 |
| Tristan Ross | It's because clang uses your host target by default | 17:10:35 |
 emily | our wrappers are target-specific | 17:10:45 |
| emily | and inject lots of target-specific things | 17:10:48 |
| Tristan Ross | Our wrapper and a lot of nixpkgs isn't built for multitarget | 17:10:50 |
| emily | it is possible to fix this and eliminate our wrappers entirely for LLVM but takes a lot of work | 17:11:02 |
| emily | (I outlined a plan for it in #stdenv:nixos.org yesterday) | 17:11:10 |
| emily | you can use clang-unwrapped if you don't need Nixpkgs dependencies, otherwise you need a proper cross package set | 17:11:26 |
| Tristan Ross | Yeah, it's something I would like to see but just isn't there yet. | 17:11:36 |
| Electro | Sounds good, that's all really helpful to know, thanks! | 17:13:55 |
|  jonhermansen joined the room. | 22:08:55 |
| 30 Jun 2025 |
 alexfmpe | trying to run a dynamicly linked pkgsCross.aarch-android executable on qemu-aarch, but it wants /system/bin/linker64
now, I see this path is present on my actual phone, and seems to be working in adb shell so it sounds like it's correct for the actual platform
rather than patchelf, I was thinking of doing qemu-aarch <the-linker> <the-executable> but don't know what to build to get an actual aarch64 linker
I do have /lib64/ld-linux-x86-64.so.2 on my x86 nixos but not /lib/ld-linux-aarch64.so.1, which I expect would be present on aarch nixos so it must be available somewhere?
| 11:54:50 |
 Artturin | In reply to @alexfmpe:matrix.org
trying to run a dynamicly linked pkgsCross.aarch-android executable on qemu-aarch, but it wants /system/bin/linker64
now, I see this path is present on my actual phone, and seems to be working in adb shell so it sounds like it's correct for the actual platform
rather than patchelf, I was thinking of doing qemu-aarch <the-linker> <the-executable> but don't know what to build to get an actual aarch64 linker
I do have /lib64/ld-linux-x86-64.so.2 on my x86 nixos but not /lib/ld-linux-aarch64.so.1, which I expect would be present on aarch nixos so it must be available somewhere?
/lib/ld... is a stub and not functional
https://search.nixos.org/options?channel=25.05&show=environment.stub-ld.enable
https://github.com/NixOS/nixpkgs/blob/nixos-25.05/nixos/modules/config/ldso.nix | 11:59:25 |
| alexfmpe | ah fair, still, the linker must be somewhere? | 12:00:16 |
| alexfmpe | do...do we not have arm nixos? | 12:01:19 |
| K900 | The Android dynamic loader isn't compatible | 12:01:41 |
| K900 | It's an entirely different ABI | 12:01:46 |
| alexfmpe | ah sadness | 12:06:13 |
| 3 Jul 2025 |
|  missbehaves joined the room. | 19:19:10 |
| missbehaves set a profile picture. | 19:21:05 |
| 4 Jul 2025 |
 @freexploit:trafkin.com | Redacted or Malformed Event | 02:33:25 |
