Add a new aarch64-freebsd double and example system, then fix include and libc to work.
This is enough to build packages like hello,
either static or dynamic.
This is useful for testing nix FreeBSD on a Raspberry Pi.
Most of the challenging parts around compiler_rt were already upstreamed months ago.
If you'd like to test, it's easy to cross build a static binary (nix build .#pkgsCross.aarch64-freebsd.pkgsStatic.hello) and copy it to a FreeBSD raspberry pi and run it.
Things done
Built on platform(s)
[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
Add a new
aarch64-freebsddouble and example system, then fix include and libc to work. This is enough to build packages likehello, either static or dynamic.This is useful for testing nix FreeBSD on a Raspberry Pi.
Most of the challenging parts around compiler_rt were already upstreamed months ago.
If you'd like to test, it's easy to cross build a static binary (
nix build .#pkgsCross.aarch64-freebsd.pkgsStatic.hello) and copy it to a FreeBSD raspberry pi and run it.Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a :+1: reaction to pull requests you find important.