| 10 May 2024 |
 rhelmot | I can think of a way to simplify this (we can filter the patches by whether they are for a relevant file in the filtered source and then apply them) but... that seems complicated. do you think it's worth it? | 22:47:30 |
 John Ericson | rhelmot: how often do we need to apply the same patch for more than one package? | 22:49:06 |
| rhelmot | rarely | 22:49:13 |
| John Ericson | if the answer is basically never we could have a dir of dirs per package? | 22:49:22 |
| John Ericson | and then just collect all the patches in each subdir? | 22:49:29 |
| John Ericson | and use that? | 22:49:31 |
| John Ericson | (or was that your middle version?) | 22:49:39 |
| rhelmot | actually I have a much better middle version | 22:50:34 |
| rhelmot | give me a day to build it | 22:50:40 |
| rhelmot | ty for poking holes in my shit | 22:51:00 |
| John Ericson | haha I think "poking holes" is too strong | 22:53:12 |
| John Ericson | also I look forward to CA derivations meaning we don't need any cleverness here :) | 22:53:27 |
| 11 May 2024 |
|  ion changed their display name from TAUPHI MORPHO to tauphi. | 06:14:25 |
 Alyssa Ross | Does anybody do native NixOS builds on any of these architectures? https://github.com/NixOS/nixpkgs/pull/308801#issuecomment-2105609075 If so please make yourself known before it becomes no longer possible to do that! | 08:38:18 |
 hexa | [
"armv5tel-linux"
"armv7a-linux"
"m68k-linux"
"microblaze-linux"
"microblazeel-linux"
"mips-linux"
"mips64-linux"
"mips64el-linux"
"mipsel-linux"
"riscv32-linux"
"s390-linux"
]
| 10:55:38 |
 trofi | My guess would be that none of them are usable natively today | 18:59:49 |
| 12 May 2024 |
| John Ericson | $ nix-shell -A pkgsCross.x86_64-openbsd.llvmPackages_17.libcxx --show-trace --keep-failed
[nix-shell:~/src/nixpkgs-master]$ $CC --rtlib=compiler-rt -print-libgcc-file-name
/usr/lib/libcompiler_rt.a
$ nix-shell -A pkgsCross.x86_64-freebsd.llvmPackages_17.libcxx --show-trace --keep-failed
[nix-shell:~/src/nixpkgs-master]$ $CC --rtlib=compiler-rt -print-libgcc-file-name
/nix/store/kgddmyqsak19cx54lwcj7l10b109gxgs-x86_64-unknown-freebsd-clang-wrapper-17.0.6/resource-root/lib/freebsd/libclang_rt.builtins-x86_64.a
| 04:45:28 |
| John Ericson | pop quiz: why are these different? | 04:45:34 |
| John Ericson | Answer: OpenBSD::getCompilerRT in clang/lib/Driver/ToolChains/OpenBSD.cpp | 04:46:03 |
| John Ericson | LLVM doing per distro hacks coded as per target is so frustrating/dissapointing | 04:46:42 |
|  aliabrar joined the room. | 04:47:03 |
| John Ericson | everyone hacking around everyone else's ideosyncrasies is not how we make the world simpler and nicer | 04:47:42 |
| John Ericson | * everyone hacking around everyone else's ideosyncrasies with more ad-hoc special cases is not how we make the world simpler and nicer | 04:47:51 |
| trofi | but it's not a libgcc file! :) | 13:55:21 |
| 13 May 2024 |
 Mic92 | How can I build a nix-shell that can run on the hostplatform, but is cross compiled? | 16:07:25 |
| Mic92 | let
nixpkgs = fetchTarball "https://github.com/NixOS/nixpkgs/archive/af8b9db5c00f1a8e4b83578acc578ff7d823b786.tar.gz"; # nixpkgs-unstable
pkgs = import nixpkgs { crossSystem = { config = "riscv64-unknown-linux-musl"; }; };
in
pkgs.pkgsHostTarget.mkShell.override { stdenv = pkgs.pkgsHostTarget.clangStdenv; } {
packages = [];
}
| 16:07:26 |
| Mic92 | That still seems to give me the build platform? | 16:07:43 |
| Mic92 | Looks like I can just "cross-compile" on the same architecture. | 16:14:04 |
| Alyssa Ross | you should get that by default | 16:17:09 |
| 14 May 2024 |
|  chrillefkrr joined the room. | 15:41:55 |
