| 19 May 2025 |
 K900 | Yes, the point of Canadian cross is that you use your slow build machine to build a cross-compiler for a fast host machine | 13:53:19 |
| K900 | And then use that cross-compiler to build packages for target | 13:53:27 |
| K900 | But faster | 13:53:31 |
 emily | you could just build the compiler on the fast host machine. | 13:55:33 |
| emily | to me the sensible use-case for Canadian cross looks like "we can only get x86 CI, not AArch64, but we want to offer AArch64 binaries of our compiler for various targets" | 13:56:23 |
| emily | in which case building an extra compiler is basically fine. | 13:56:32 |
| 21 May 2025 |
|  WeetHet changed their profile picture. | 10:59:09 |
| 22 May 2025 |
 rhelmot | perl modules cross is an irredeemable nightmare | 22:29:14 |
| rhelmot | I cannot figure out how to get it to build extension modules that do not link the build platform's libc... | 22:30:16 |
| rhelmot | new problem - https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/misc/gdb/default.nix#L40 I don't think this is correct, since when I build gdb with buildPlatform = linux and hostPlatform = freebsd, this ends up being a linux path pulling glibc into the closure, which is completely useless. | 22:56:58 |
| rhelmot | does anyone know how to test whatever that line is supposed to support? | 22:57:41 |
| rhelmot | https://github.com/NixOS/nixpkgs/pull/73574 concerning... | 23:03:10 |
| 23 May 2025 |
 trofi | I thin it should auto-load .py gdb script for target libstdc++ when yoiu load c++ based programs to debug | 14:53:59 |
| trofi | /nix/store/7c0v0kbrrdc2cqgisi78jdqxn73n3401-gcc-14.2.1.20250322-lib/lib/libstdc++.so.6.0.33-gdb.py | 14:55:05 |
| trofi | And given that it does not work on gdb gdb I think it is missing /lib subdir. | 14:59:06 |
| 24 May 2025 |
|  fromtheeast710 joined the room. | 05:09:22 |
|  neobrain joined the room. | 14:01:33 |
| neobrain | Hi! Having a bit of trouble getting off the ground with cross-compiling in a nix-shell. I'm working on a mixed-architecture project (main component runs on ARM64, but additionally some x86-64 executables must be built) and I can't use binfmt_misc/qemu.
Do nix/nixpkgs still provide a simple way to install a cross-compiler (built for ARM64 and targeting x86-64) that I can manually invoke in a CMakeToolchain? | 14:46:06 |
| neobrain | ... of course as usual, after an hour of looking the answer presents itself right after asking: x86Pkgs.buildPackages.gcc seems to be what I'm looking for (instead of x86Pkgs.gcc) | 14:48:31 |
| neobrain | * ... of course as usual, after an hour of looking the answer presents itself right after asking: pkgsCross.gnu64.buildPackages.gcc seems to be what I'm looking for (instead of pkgsCross.gnu64.gcc) | 14:48:58 |
| neobrain | Any idea how I can build a sysroot with libc/libstdc++ headers? I know I need to use pkgs.buildEnv, but I'm struggling to find the right packages that contain the headers | 18:15:44 |
| neobrain | Looks like libgcc.out is the one | 18:37:28 |
| neobrain | * Looks like libgcc.out is the one, or rather pkgs.pkgsCross.gnu64.gcc-unwrapped for the cross-compiler | 18:45:41 |
| 27 May 2025 |
|  c2vi set a profile picture. | 11:17:35 |
| 29 May 2025 |
|  emily 🐾 changed their profile picture. | 22:22:54 |
| 23 Sep 2025 |
|  Rick (Mindavi) left the room. | 07:35:15 |
| 29 May 2025 |
| emily 🐾 changed their profile picture. | 22:33:47 |
| emily 🐾 changed their profile picture. | 22:34:14 |
| 31 May 2025 |
| trofi left the room. | 13:48:53 |
| 1 Jun 2025 |
|  htdar joined the room. | 11:02:21 |
