| 20 Sep 2023 |
 rhelmot | I've added to my PR the ability to parameterize the freebsd packages so they can be cross compiled for either freebsd13 or freebsd14. I can now compile all the inputs necessary for the freebsd stdenv. what's the protocol on being able to access a cross-compiled package from a native-booting stdenv? I assume there's some magic somewhere to make it so the hashes line up, but I'm not sure what that would look like. | 07:03:37 |
| rhelmot | * I've added to my PR the ability to parameterize the freebsd packages so they can be cross compiled for either freebsd13 or freebsd14. I can now cross compile all the inputs necessary for the freebsd stdenv. what's the protocol on being able to access a cross-compiled package from a native-booting stdenv? I assume there's some magic somewhere to make it so the hashes line up, but I'm not sure what that would look like. | 07:04:12 |
| rhelmot | if the answer is "no such thing", what exactly is john's vision in terms of being able to use cross compilation to generate substitutes such that nix can run on freebsd and actually download them as needed? | 07:10:35 |
 Alyssa Ross | You can import <nixpkgs> { localSystem = "x86_64-linux"; crossSystem = "x86_64-freebsd"; } or something and get the same packages | 08:07:12 |
| Alyssa Ross | but if I understand correctly, what John means to do is to cross compile some packages, and use them to generate a bootstrap tarball for the native stdenv, not to substitute them directly. | 08:07:47 |
| Alyssa Ross | Also hi! Sorry, I haven't had much of a chance to look at your work so far. | 08:07:56 |
| Alyssa Ross | Re: FreeBSD version: the reason we have "13" in the triples is because we misunderstood how backwards compatible FreeBSD is. Probably it would be fine to just target a single version. | 08:08:57 |
| rhelmot | Can you elaborate on the misunderstanding? I certainly encountered binary incompatibilities (potentially solved by nix and strict library versioning?) while upgrading from 13 to 14. | 12:36:06 |
| rhelmot | Also hi :) | 12:36:10 |
| rhelmot | If that’s the vision, why can the bootstrap binaries not be generated by the (fully booted?) impure stdenv? This definitely sounds like a situation where I’m misunderstanding the benefits of purity, but to my knowledge it would be solved by a bunch of binary auditing. | 12:40:14 |
| rhelmot | * Can you elaborate on the misunderstanding? I certainly encountered binary incompatibilities (upgraded my kernel but not my userland on accident and very little would still run? I hope I’m misremembering that) while upgrading from 13 to 14. | 12:47:19 |
| rhelmot | there's a very easy way to test the binary compatibility thing. I can just copy some of the 13 binaries onto my 14 system (and vice versa with a VM) and see what happens | 13:28:05 |
| Alyssa Ross | I'll see if I can find the conversation | 13:28:47 |
 7c6f434c | I believe FreeBSD promises nothing on major-version kernel-libc mixing. Does anything survive anyway is an empirical question, of course | 15:05:53 |
| rhelmot | side note: if nix-build ./nixpkgs --argstr crossSystem x86_64-freebsd14 --show-trace -A bash and nix-build ./nixpkgs --show-trace -A pkgsCross.x86_64-freebsd14.bash are different did I do something wrong? | 15:08:37 |
| rhelmot | * ~~side note: if nix-build ./nixpkgs --argstr crossSystem x86_64-freebsd14 --show-trace -A bash and nix-build ./nixpkgs --show-trace -A pkgsCross.x86_64-freebsd14.bash are different did I do something wrong?~~ (edit: figured it out. gotta do --arg with all of the example system attributes, including useLLVM) | 18:48:02 |
| 21 Sep 2023 |
|  dedmunwalk joined the room. | 23:05:26 |
| 22 Sep 2023 |
 ash (it/its) 🏳️⚧️ | @Alyssa Ross btw, i have a patch that fixes your pr #233470. could you take a look and maybe pull that into your pr? | 22:52:35 |
| 23 Sep 2023 |
| Alyssa Ross | ooh | 07:25:19 |
| Alyssa Ross | this looks like great work | 07:25:23 |
| Alyssa Ross | I will try to take a look but can't promise atm | 07:25:32 |
|  Snuupy joined the room. | 10:17:48 |
| 24 Sep 2023 |
|  mib 🥐 changed their profile picture. | 12:20:53 |
| 25 Sep 2023 |
|  moody joined the room. | 04:10:16 |
|  @janik0:matrix.org joined the room. | 06:42:50 |
| rhelmot | is 150MB too big for the freebsd bootstrap tools? I have a minimal working set rn but because it uses clang libllvm and libclang are eating a lot of that space... | 13:39:12 |
| rhelmot | * is 150MB compressed too big for the freebsd bootstrap tools? I have a minimal working set rn but because it uses clang libllvm and libclang are eating a lot of that space... | 13:39:21 |
 raitobezarius | Well it's not a minimal bootstrap but this is a reasonable bootstrap I'd say personally | 13:43:06 |
| rhelmot | error: builder for '/nix/store/bsfkbj4h494i1n8lzdfyhrp9xk6pnxir-gettext-0.21.1.drv' failed with exit code 1;
last 1 log lines:
> build input /nix/store/cbls2b0w8r4gxan0ifdk6pksramy0hfg-bootstrap-tools/nix/store/cbls2b0w8r4gxan0ifdk6pksramy0hfg-bootstrap-tools does not exist
For full logs, run 'nix log /nix/store/bsfkbj4h494i1n8lzdfyhrp9xk6pnxir-gettext-0.21.1.drv'.
does this indicate a bug in nix? I "fixed" it by adjusting some overrides but I don't know why this would ever be produced. the builder isn't even getting run.
| 17:15:29 |
| raitobezarius | It seems like you are building the wrong path | 17:53:32 |
