qbit/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
nixpkgs/pkgs/stdenv/darwin
History
Randy Eckenrode 484eca6cec
llvmPackages.llvm-manpages: fix eval on Darwin 
Darwin prevents curl from being used in the Darwin bootstrap. The man
pages are built for darwin.binutils-unwrapped, but overrides are applied
only there, leaving plain llvmPackages.llvm-manpages broken.

The fix is to move the override to the llvmPackages package set.
2024-11-20 18:27:53 -05:00
..
bootstrap-files
bootstrap-tools.nix freshBootstrapTools.bootstrapTools: extract as a package 2024-08-02 16:08:15 -07:00
default.nix llvmPackages.llvm-manpages: fix eval on Darwin 2024-11-20 18:27:53 -05:00
make-bootstrap-tools.nix freshBootstrapTools: remove rec in favor of explicit attrset building 2024-08-02 16:11:03 -07:00
override-sdk.nix overrideSDK: update for the new SDK 2024-10-10 16:23:08 -04:00
README.md
stdenv-bootstrap-tools.nix freshBootstrapTools.bootstrapTools: update for new SDK pattern 2024-10-11 18:40:58 -04:00
test-bootstrap-tools.nix freshBootstrapTools.bootstrapTools: update for new SDK pattern 2024-10-11 18:40:58 -04:00

README.md

Darwin stdenv design goals

There are two more goals worth calling out explicitly:

  1. The standard environment should build successfully with sandboxing enabled on Darwin. It is fine if a package requires a sandboxProfile to build, but it should not be necessary to disable the sandbox to build the stdenv successfully; and
  2. The output should depend weakly on the bootstrap tools. Historically, Darwin required updating the bootstrap tools prior to updating the version of LLVM used in the standard environment. By not depending on a specific version, the LLVM used on Darwin can be updated simply by bumping the definition of llvmPackages in all-packages.nix.

Updating the stdenv

There are effectively two steps when updating the standard environment:

  1. Update the definition of llvmPackages in all-packages.nix for Darwin to match the value of llvmPackages.latest in all-packages.nix. Timing-wise, this done currently using the spring release of LLVM and once llvmPackages.latest has been updated to match. If the LLVM project has announced a release schedule of patch updates, wait until those are in nixpkgs. Otherwise, the LLVM updates will have to go through staging instead of being merged into master; and
  2. Fix the resulting breakage. Most things break due to additional warnings being turned into errors or additional strictness applied by LLVM. Fixes may come in the form of disabling those new warnings or by fixing the actual source (e.g., with a patch or update upstream). If the fix is trivial (e.g., adding a missing int to an implicit declaration), it is better to fix the problem instead of silencing the warning.