Skip to content

doc/rl-2511: note removal of llvmPackages from haskell.packages.* #442037

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sternenseemann merged 1 commit into from
Sep 11, 2025
Merged

doc/rl-2511: note removal of llvmPackages from haskell.packages.* #442037

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions doc/release-notes/rl-2511.section.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,12 @@
The latter was probably broken anyway.
If there is interest in restoring support for these architectures, it should be possible to cross鈥恈ompile a bootstrap GHC binary.

- `haskellPackages` and the package sets under `haskell.packages` no longer expose an `llvmPackages` attribute,
though it can still be accessed via `ghc.llvmPackages` (from the same package set).
Haskell packages usually only need to depend on an LLVM version matching GHC if they force the use the LLVM
backend even if NCG is available. In this case, it is best to use the `forceLlvmCodegenBackend` helper.
In all other cases, like linking against `libLLVM`, Haskell packages should use the appropriate version of `llvmPackages` from `pkgs`.

- `base16-builder` node package has been removed due to lack of upstream maintenance.

- `python3Packages.bjoern` has been removed, as the upstream is unmaintained and it depends on a 14-year-old version of http-parser with numerous vulnerabilities.
Expand Down
Loading