3
0
Fork 0
forked from mirrors/nixpkgs
nixpkgs/nixos/doc/manual/release-notes/rl-2205.section.md
sternenseemann 558da925f3 ghc: make sure top level exposed GHC is always host->target
See the added comment in all-packages.nix for a more detailed
explanation. This makes the top-level GHC different from
haskellPackages.ghc (which is build->host and used for building the
package set), but more consistent with gcc, gnat etc.

Specifically, pkgsCross.${platform}.buildPackages.ghc will now be a
cross-compiler instead of a native build->build compiler.

Since this change has a slight chance of being disruptive, add a note to
the changelog.
2021-11-25 20:18:25 +01:00

1.2 KiB

Release 22.05 (“Quokka”, 2022.05/??)

In addition to numerous new and upgraded packages, this release has the following highlights:

  • Support is planned until the end of December 2022, handing over to 22.11.

Highlights

New Services

Backward Incompatibilities

  • pkgs.ghc now refers to pkgs.targetPackages.haskellPackages.ghc. This only makes a difference if you are cross-compiling and will ensure that pkgs.ghc always runs on the host platform and compiles for the target platform (similar to pkgs.gcc for example). haskellPackages.ghc still behaves as before, running on the build platform and compiling for the host platform (similar to stdenv.cc). This means you don't have to adjust your derivations if you use haskellPackages.callPackage, but when using pkgs.callPackage and taking ghc as an input, you should now use buildPackages.ghc instead to ensure cross compilation keeps working (or switch to haskellPackages.callPackage).

Other Notable Changes