Cardano Updates

zlib doesn't cross-compile cleanly to wasm:

  * gzguts.h only `#include <errno.h>` when NO_STRERROR is unset, but
    gzread.c / gzwrite.c use errno / EAGAIN / EWOULDBLOCK unconditionally.
    zlib's configure probes strerror by compiling *and running* a test, which
    can't run when cross-compiling to wasm, so it defines NO_STRERROR (even
    though wasi-libc has strerror) and the gz* sources fail to compile with
    "use of undeclared identifier 'errno'".  Always include errno.h.

  * zlib sets NIX_LDFLAGS = "--undefined-version" whenever the linker is lld
    (to counter lld 16+'s --no-undefined-version default for its shared-lib
    version script).  wasm-ld is lld-based but rejects that flag, and we build
    static anyway, so drop it.

The wasm testWrapper ran `wasmtime <test>` with no `--dir`, so WASI granted the
module zero filesystem access and any test reading its data-files
(getDataFileName, under <pkg>-data/share/...) or a source-relative file failed
with a misleading "does not exist".  Preopen `/nix/store` and `.` so those
reads work.

The check-datadir test also exercises a build-tool-depends exe via readProcess,
which WASI cannot do (no process spawning -> "unsupported operation").  Guard
that check to non-wasm targets; the datadir and source-relative-file checks
still run under wasm.

FreeType's freetype2.pc advertises a libtool/ABI version (e.g. 26.2.20) that
is deliberately decoupled from the release .version (e.g. 2.13.3), per
freetype's docs/VERSIONS.TXT.  `pkg-config --modversion freetype2` returns the
libtool number, so plan-to-nix must report the same value; otherwise the v2
slice's UnitId (which folds the resolved freetype2 version into
pkgHashPkgConfigDeps) forks, taking every transitive consumer
(gi-freetype2 -> gi-harfbuzz -> gi-pango -> gi-gdk3 -> gi-gtk3 -> ...) with it.

Add a `passthru.pc-version` table (the known release->libtool rows from
VERSIONS.TXT), falling back to .version with a warning for unknown releases.
This does not alter freetype's derivation, so it neither rebuilds nor forces a
build of freetype during planning.

When `build-tool-depends` is on, lib:ghc names `genprimopcode` and
`deriveConstants` as exe build-tools.  These live in the GHC source tree, not
on hackage, so cabal could only find them by chance on PATH.  Expose them
(alongside the `compiler/` subdir) as reinstallable source-repository-packages
from the GHC source, wired through inputMap, so cabal satisfies the goals
normally.

This removes the need for the `packages.ghc...build-tools = mkForce [alex
happy]` override, so drop it from configuration-nix.nix.

builderVersion = 2 runs a test's installed binary directly (not via
`cabal v2-test`) in an empty dir with only runtime libs on PATH, so tests
that rely on the environment cabal normally provides failed.  Bring the v2
`check` (lib/check.nix) in line with v1 / cabal v2-test:

- Set each installed package's `<pkg>_datadir` (the env var Cabal's
  `Paths_<pkg>` consults) to the `share` dir the slice stages under
  `$out/store/ghc-*/<unit>/share`, so `getDataFileName` finds `data-files`
  (the compiled-in datadir is an ephemeral build-time cabal dir).

- Put the component's `build-tool-depends` (`executableToolDepends`,
  including same-package exes a test spawns) on PATH, so e.g. a test that
  spawns its package's exe no longer fails with `spawnProcess: ... does not
  exist`.

- Run the test from a writable copy of the package source subdir
  (`passthru.srcSubDirPath`), so tests reading source-relative files
  (golden files / fixtures) find them — mirroring v1's unpack + cd.

All three happen before `preCheck` so a project's own `preCheck` can still
override them.  Exes are unaffected (they install to the store with a
correct, persistent datadir).

Adds the `check-datadir` test: a library package shipping a data-file, a
source-relative file, and a build-tool exe, with a test-suite that reads /
spawns all three — run under both builderVersion 1 and 2.

When GHC's configure is regenerated here via autoreconfHook using a host
autoconf >= 2.72, AC_PROG_CC probes for and appends the newest C standard
flag the compiler accepts (e.g. -std=gnu23 with clang 21) to $CC. GHC then
bakes $CC verbatim into the "C compiler command" / "C++ compiler command" /
"Haskell CPP command" settings fields. On aarch64-darwin with nixpkgs
nixos-26.05 (autoconf 2.73, clang 21) GHC therefore tries to exec a binary
literally named "cc -std=gnu23" and fails at configurePhase of the first
package it compiles:

  ghc-9.8.4: could not execute: /nix/store/...-clang-wrapper-21.1.8/bin/cc -std=gnu23

nixpkgs' own GHC is unaffected because it ships GHC's pre-generated configure
(no autoreconf), so the std flag never lands in the command field.

Move the std flag out of each command field into its matching flags field in
postInstall, mirroring the existing Windows dllwrap/windres settings fixup.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

Introduces a .small passthru variant on GHC derivations that opts out of
profiling libraries and Haddock documentation, significantly reducing closure
size for CI, Docker, and cross-compilation toolchain use cases.

Also fixes a pre-existing bug where `enableLibraryProfiling = false` had no
effect on Hadrian builds (GHC 9.4+): the `+no_profiled_libs` flavour
transformer was only applied for GHCJS/Wasm targets, silently ignoring the
parameter for all other platforms.

Changes:
- Add `enableHaddockDocs` parameter (default true, fully backwards-compatible)
- Fix legacy make build: HADDOCK_DOCS=NO now also honours enableHaddockDocs
- Fix Hadrian: +no_profiled_libs applied whenever enableLibraryProfiling=false
- Hadrian: --docs=nothing when enableHaddockDocs=false, no-sphinx otherwise
- Make sphinx and hscolour nativeBuildInputs conditional on enableHaddockDocs
- Add .small passthru variant (enableLibraryProfiling=false, enableHaddockDocs=false)

Usage: pkgs.haskell-nix.compiler.ghc967.small

* pkg-config: add pc-version to fix v2 UnitId fork for pkgconfig-depends packages

allPkgConfigWrapper (used by plan-to-nix) reports pkg-config --modversion
from the nixpkgs derivation .version, but a builderVersion = 2 slice runs
the real pkg-config, which reads the .pc Version: field.  When these differ
the slice's UnitId forks from plan-nix's (the resolved pkgconfig-dep version
is folded into pkgHashPkgConfigDeps), failing the slice's expected-package
check.  systemd is the motivating case: libsystemd.pc reports the major
version (258/259) but .version has a patch component (258.5/259.3), which
broke libsystemd-journal.

- getVersion prefers an optional pc-version attribute over .version
- override systemd to set pc-version = lib.versions.major version
- add the pkgconf-pc-version test asserting pc-version == pkg-config
  --modversion (discovers pc-version modules via evalPackages to avoid
  forcing the whole map against exotic target pkgs; disabled where no
  pc-version package is buildable, e.g. musl/static/wasm/windows)

* pkgconf-pc-version: gate on glibc, not just linux

The test was enabled on android-prebuilt targets (isLinux && !isMusl &&
!isStatic), where it tried to build systemd for a bionic libc target and
failed with a dependency error.  systemd only builds on glibc, so gate the
systemd module set on hostPlatform.libc == "glibc" (excludes android/bionic,
musl, Windows, wasm) plus !isStatic.

The test was enabled on android-prebuilt targets (isLinux && !isMusl &&
!isStatic), where it tried to build systemd for a bionic libc target and
failed with a dependency error.  systemd only builds on glibc, so gate the
systemd module set on hostPlatform.libc == "glibc" (excludes android/bionic,
musl, Windows, wasm) plus !isStatic.

allPkgConfigWrapper (used by plan-to-nix) reports pkg-config --modversion
from the nixpkgs derivation .version, but a builderVersion = 2 slice runs
the real pkg-config, which reads the .pc Version: field.  When these differ
the slice's UnitId forks from plan-nix's (the resolved pkgconfig-dep version
is folded into pkgHashPkgConfigDeps), failing the slice's expected-package
check.  systemd is the motivating case: libsystemd.pc reports the major
version (258/259) but .version has a patch component (258.5/259.3), which
broke libsystemd-journal.

- getVersion prefers an optional pc-version attribute over .version
- override systemd to set pc-version = lib.versions.major version
- add the pkgconf-pc-version test asserting pc-version == pkg-config
  --modversion (discovers pc-version modules via evalPackages to avoid
  forcing the whole map against exotic target pkgs; disabled where no
  pc-version package is buildable, e.g. musl/static/wasm/windows)