| 3 Jan 2024 |
|  @ftchrist:matrix.org changed their display name from Frédéric Christ (DECT 4842) to Frédéric Christ. | 11:30:38 |
| 4 Jan 2024 |
|  thetootler joined the room. | 06:24:56 |
| 5 Jan 2024 |
|  @palo:xaos.space joined the room. | 08:36:13 |
| @palo:xaos.space left the room. | 08:36:53 |
| 7 Jan 2024 |
|  hacker1024 joined the room. | 23:55:41 |
| 9 Jan 2024 |
|  matthewcroughan - nix.how changed their display name from matthewcroughan - Linux 6.7 When to matthewcroughan. | 08:40:32 |
| 10 Jan 2024 |
 John Ericson | does anyone know what fixed BSD evaluation master relative 23.11? | 23:24:07 |
| John Ericson | want to backport it | 23:24:10 |
| 11 Jan 2024 |
 trofi | Evals should be easy to bisect. Do you know specific failures or a command to run on Linux? | 09:06:00 |
| 13 Jan 2024 |
| John Ericson | trofi: yeah good point. nix-instantiate -A pkgsCross.x86_64-netbsd.stdenv should suffice. | 00:32:41 |
| trofi | My bet is on https://github.com/NixOS/nixpkgs/pull/268204 | 00:47:35 |
| trofi | Cherry-picking 92ec26ce8d59d6856fb4f5ee4d1b74c654ca6eda is enough to fix instantiation. | 00:48:22 |
| trofi | John Ericson: ^ | 00:48:59 |
| John Ericson | trofi: thank you! | 01:36:52 |
| John Ericson | :) | 01:36:55 |
| John Ericson | now Nix can finally upgrade to 23.11, perhaps | 01:37:08 |
| John Ericson | but do need to wait for somethings to make it off stanging maybe) | 01:37:17 |
| John Ericson | and I think I have a better fix for that too, since the CVS thing doesn't really look darwin-specific | 01:49:20 |
 Alyssa Ross | Did we ever fix FreeBSD? | 09:45:23 |
| Alyssa Ross | It regressed with the LLVM update | 09:45:29 |
 samueldr | so uh, I have a weird exotic thing I might need some hints or help, and there's enough gaps in my knowledge of cross in general that I'm not even sure where to start from (the trivial attempts failed for different reasons at different stages) | 23:07:14 |
| samueldr | it's a target that uses --target=i386-unknown-gnu from stock 2.95.3 gcc, which works with current binutils configured for the same target, but the system libraries to link with are all just binaries | 23:08:55 |
| samueldr | I have built their SDK samples through a (bad) Nix setup though | 23:09:35 |
| samueldr | I can't expect many things from Nixpkgs to work, if anyhing other than the toolchain, but my goal here is (as a learning experience, there's no stakes here) to try and use as much of the Nixpkgs tooling to get stuff building, and I'm not exactly sure where to start from | 23:11:11 |
 raitobezarius | what is your desired next step? | 23:18:06 |
| raitobezarius | build a package with that? | 23:18:08 |
| samueldr | with the target/host platform dance handled through Nixpkgs machinery | 23:18:33 |
| raitobezarius | I guess the first goal is to have a "system" for it in nixpkgs so that you could do import <nixpkgs> { system = "my-weird-target"; } ? | 23:18:36 |
| raitobezarius | to do that you can hm | 23:18:43 |
| samueldr | you can do it directly at Nixpkgs import without a name for the weird target | 23:18:58 |
