- May 23, 2022
-
-
Matthew Pickering authored
This seems to fail on the ancient version of bash present on CentOS (cherry picked from commit 209d7c69)
-
Matthew Pickering authored
The centos docker image lacks the sphinx builder so we disable building sphinx docs for these jobs. Fixes #21580 (cherry picked from commit a05b6293)
-
Matthew Pickering authored
The release flavour is essentially the same as the perf flavour currently but also enables `-haddock`. I have hopefully updated all the relevant places where the `-perf` flavour was hardcoded. Fixes #21486
-
- May 21, 2022
-
-
Ben Gamari authored
Debian 9's toolchain seems to break when split sections is enabled. This reverts commit ab4d7420.
-
- May 18, 2022
-
-
We still build Deb9 bindists for now due to Ubuntu 18 and Linux Mint 19 not being at EOL until April 2023 and they still need tinfo5. Fixes #21469 (cherry picked from commit 0fdf44a8)
-
This adds a CI job (hackage-doc-tarball) which generates the necessary tarballs for uploading libraries and documentation to hackage. The release script knows to download this folder and the upload script will also upload the release to hackage as part of the release. The `ghc_upload_libs` script is moved from ghc-utils into .gitlab/ghc_upload_libs There are two modes, preparation and upload. * The `prepare` mode takes a link to a bindist and creates a folder containing the source and doc tarballs ready to upload to hackage. * The `upload` mode takes the folder created by prepare and performs the upload to hackage. Fixes #21493 Related to #21512 (cherry picked from commit daac5040)
-
Ben Gamari authored
To ensure that the build benefits from Hadrian's usual logic for building packages, avoiding #21409. Closes #21409. (cherry picked from commit 4d189db9)
-
Ben Gamari authored
Previously `test.mk` would try to determine whether the dynamic, profiling, and vanilla library ways are available by searching for `PrimOpWrappers.{,dyn_,p_}hi` in directory reported by `ghc-pkg field ghc-prim library-dirs`. However, this is extremely fragile as there is no guarantee that there is only one library directory. To handle the case of multiple `library-dirs` correct we would have to carry out the delicate task of tokenising the directory list (in shell, no less). Since this isn't a task that I am eager to solve, I have rather moved the detection logic into the testsuite driver and instead perform a test compilation in each of the ways. This should be more robust than the previous approach. I stumbled upon this while fixing #20579. (cherry picked from commit cd3f420f)
-
Ben Gamari authored
(cherry picked from commit c556cbf3)
-
Ben Gamari authored
The package-specific include directories in Settings.Builders.Common.cIncludeDirs are now redundant since they now come from Cabal. Closes #20566. (cherry picked from commit a216403e)
-
Ben Gamari authored
Previously we only took `extraLibDirs` and friends from the package description, ignoring any contribution from the `LocalBuildInfo`. Fix this. Fixes #20566. (cherry picked from commit 2b21c3fc)
-
This bumps the time submodule to the 1.12.2 release. Fixes #21571 (cherry picked from commit 70f52443)
-
Ben Gamari authored
Both #20878 and #21196 were caused by unwanted dynamic dependencies being introduced by boot libraries. Ensure that we catch this in CI by attempting to run GHC in an environment with a minimal PATH. (cherry picked from commit fcc7dc4c)
-
(cherry picked from commit 5b791ed3)
-
When passed `--use-system-libffi` then we shouldn't copy and install the headers from the system package. Instead the headers are expected to be available as a runtime dependency on the users system. Fixes #21485 #21487 (cherry picked from commit fec3e7aa)
-
This has high potential for oversubcribing as many haddock jobs can be spawned in parralel which will each request the given number of capabilities. Once -jsem is implemented (#19416, !5176) we can expose that haddock via haddock and use that to pass a semaphore. Ticket #21136 (cherry picked from commit 9d8f44a9)
-
In the make bindists we generate documentation in docs/ghc-<VER> but the hadrian bindists generate docs/ghc/ so the path to the GHC API docs was wrong in the index.html file. Rather than make the hadrian and make bindists the same it was easier to assume that if you're using the mkDocs script that you're using hadrian bindists. Fixes #21509 (cherry picked from commit 68d1ea5f)
-
The splitSections transformer has been broken since -dynamic-too support was implemented in hadrian. This is because we actually build the dynamic way when building the dynamic way, so the predicate would always fail. The fix is to just always pass `split-sections` even if it doesn't do anything for a particular way. Fixes #21138 (cherry picked from commit 142a73d9)
-
There have been quite a few situations where jobs.yaml has been out of date. It's better to add a CI job which checks that it's right. We don't want to use a staged pipeline because it obfuscates the structure of the pipeline. (cherry picked from commit aacb15a3)
-
We need to distribute the source tarball so we should generate it in the CI pipeline. (cherry picked from commit ced4689e)
-
(cherry picked from commit 6e69964d)
-
(cherry picked from commit c7ee0be6)
-
Fixes #21373 (cherry picked from commit 55c84123)
-
(cherry picked from commit 2dcdf091)
-
We also disable the stage1 testing which is broken. Related to #21072 (cherry picked from commit 50d78d3b)
-
(cherry picked from commit 2c00d904)
-
It's quite nice we can do this by mostly deleting code Fixes #21373 (cherry picked from commit 75bf1337)
-
Ben Gamari authored
Bumps text and exceptions submodules due to bounds.
-
Ben Gamari authored
We previously only checked the stage 1/2 compiler for --target support. We got away with this for quite a while but it eventually caught up with us in #21579, where `bytestring`'s new NEON implementation was unbuildable on Darwin due to Rosetta's seemingly random logic for determining which executable image to execute. This lead to a confusing failure to build `bytestring`'s cbits, when `clang` tried to compile NEON builtins while targetting x86-64. Fix this by checking CC_STAGE0 for --target support. Fixes #21579. (cherry picked from commit 222eb83e)
-
- May 16, 2022
-
-
Ben Gamari authored
Now since `bytestring` depends upon `template-haskell` we must rebulid it since the boot compiler's `template-haskell` may not match that of the compiler being built.
-
The lack of INLNE arity was exposed by #21531. The fix is simple enough, if a bit clumsy. (cherry picked from commit cebf31ff)
-
Ben Gamari authored
Resolves ghc/ghc#19127 (cherry picked from commit 208c67af)
-
- May 13, 2022
-
-
Pavol Vargovčík authored
-
Pavol Vargovčík authored
-
-
Pavol Vargovčík authored
-
Pavol Vargovčík authored
-
Pavol Vargovčík authored
-