haskellPackages: update stackage and hackage#209112
Conversation
Previously, we would try to calculate the name of buildPackages.stdenv.cc and then just hope that it is in PATH somehow. This definitely doesn't work in all cases. The new approach is to add buildPackages.stdenv.cc to depsBuildBuild which also populates CC_FOR_BUILD which we can directly re-use.
This line may look odd, but we should not set ghc.isGhcjs if we are using the JavaScript backend. It is a normal cross backend and no special code is required to make it work, i.e. everything will be named as it would be normally. Additionally, passing --ghcjs to Cabal will make it do the wrong thing. We need to, of course, stop strip from being thrown at the JS objects in both cases.
The JavaScript backend emits `#!/usr/bin/env node` shebangs we need to take care off using patchShebangs in fixupPhase.
This commit has been generated by maintainers/scripts/haskell/update-hackage.sh
This commit has been generated by maintainers/scripts/haskell/regenerate-hackage-packages.sh
This commit has been generated by maintainers/scripts/haskell/update-hackage.sh
This commit has been generated by maintainers/scripts/haskell/regenerate-hackage-packages.sh
It should be just below the current output limit, but we'll see. If it doesn't fit, we may have to disable profiling objects.
haskellPackages.mkDerivation: make work in pkgsCross.ghcjs
|
Any chance for another hackage/stackage bump? |
This commit has been generated by maintainers/scripts/haskell/update-hackage.sh
This commit has been generated by maintainers/scripts/haskell/regenerate-hackage-packages.sh
|
Sure, done! |
|
@domenkozar The cachix override diverged between master and haskell-updates, and I am not certain what the correct resolution is. Would you mind fixing it? (Edit: Nevermind, you were faster.) |
|
Wow, the error message I get, when I try to build nix-diff with a jailbreak is something I have never seen from ghc. |
|
cc @Player-205 |
nvfetcher: add nix-prefetch-docker to PATH
|
|
|
Seems like the last broken build is ghcjs on darwin. |
That's not ghcjs! Seems like a GHC configure bug on darwin, we'll see. Not a regression, so not a blocker. Edit: Have a fix for aarch64-linux (likely), darwin remains a mystery… |
GHC ships a [modified] config.sub so that js-unknown-ghcjs is accepted by autotools. For some platforms, we automatically update config.sub from upstream's source in order to prevent that builds fail when we use an outdated config.sub. In this case of course the perfectly up to date config.sub would reject the target platform we are trying to use, so we must disable this mechanism for now. I have asked in the GHC IRC channel if there are any plans on upstreaming the platform. It would be nice if were able to drop this change in the future.
This commit has been generated by maintainers/scripts/haskell/mark-broken.sh
…ckage
The package is needed by tasty on a subset of architectures. Quoting
upstream `.cabal` file:
if(!arch(x86_64) && !arch(aarch64))
build-depends:
unbounded-delays >= 0.1
This fails the build on i686 (a wine depend via shellcheck):
Setup: Encountered missing or private dependencies:
unbounded-delays >=0.1
The change pulls unbounded-delays for mentioned targets.
Co-authored-by: sternenseemann <sternenseemann@systemli.org>
…fig-sub-rollback pkgsCross.ghcjs.haskellPackages.ghc: don't revert edited config.sub
pkgsi686Linux.haskellPackages.tasty: pull missing unbounded-delays pa…
This Merge
This PR is the regular merge of the
haskell-updatesbranch intomaster.This branch is being continually built and tested by hydra at https://hydra.nixos.org/jobset/nixpkgs/haskell-updates. You may be able to find an up-to-date Hydra build report at cdepillabout/nix-haskell-updates-status.
We roughly aim to merge these
haskell-updatesPRs at least once every two weeks. See the @NixOS/haskell team calendar for who is currently in charge of this branch.haskellPackages Workflow Summary
Our workflow is currently described in
pkgs/development/haskell-modules/HACKING.md.The short version is this:
haskell-updates(normally at the beginning of a merge window).haskell-updatesintomasterevery two weeks.mergeablejob is succeeding on hydra.maintainedpackage is still broken at the time of merge, we will only merge if the maintainer has been pinged 7 days in advance. (If you care about a Haskell package, become a maintainer!)This is the follow-up to #208421. Come to #haskell:nixos.org if you have any questions.