Skip to content

merge queue: embarking master (beba231), #11450 and #11386 together#11624

Closed
mergify[bot] wants to merge 4 commits intomasterfrom
mergify/merge-queue/96f5aa1678
Closed

merge queue: embarking master (beba231), #11450 and #11386 together#11624
mergify[bot] wants to merge 4 commits intomasterfrom
mergify/merge-queue/96f5aa1678

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Mar 15, 2026

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch master (beba231), #11450 and #11386 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #11386.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Validate post job
    • check-neutral = Validate post job
    • check-skipped = Validate post job
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

Required conditions to stay in the queue:

---
checking_base_sha: 6b01dfe93adcff25930ebb031cfac7384eb87caf
previous_failed_batches: []
pull_requests:
  - number: 11386
...

mpickering and others added 4 commits March 13, 2026 16:13
The new `Cabal` and `cabal-install` option tells GHC to build a
bytecode library.

* When GHC is invoked, bytecode objects are also produced.
* A bytecode library is created during linking.
* The bytecode library is installed when the package is installed.
* The `bytecode-library-dirs` field can be populated to instruct GHC
  where to find the bytecode library for a package. (This can be useful
  if the bytecode libraries are distributed separately from the other
  libraries).
* The `--bytecodelibdir` option can be used to specify a separate
  install location for bytecode libraries.

The bytecode object files are produced alongside an existing build way.
They are prioritised in this order (`-dyn-too`, `-dynamic`, `-static`).

Bytecode libraries can't be produced standalone at the moment. You have
to produce them alongside an existing build way. This is due to
limitations in GHC.

At the moment, there is not support implemented for creating profiled
bytecode libraries.

Implements haskell/cabal-proposals#2

Fixes #11188
The cause of this bug was when ProgramDb is serialised (by caching), the
`UnconfiguredPrograms` are discarded. `cabal-install` resolves this by
adding back the relevant `UnconfiguredPrograms` in `compilerProgramDb`.

The cause of the bug was the order programs were added back. I have
clarified the logic of the function now to:

1. Add back all unconfigured programs, and handle an explicit ghc-pkg
   path.
2. Then configure ghc-pkg and check it's the right version.

This makes sure that the user-supplied path is honoured in both
situations.

Fixes #11373
@mergify mergify bot closed this Mar 15, 2026
@mergify mergify bot deleted the mergify/merge-queue/96f5aa1678 branch March 15, 2026 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant