-
Notifications
You must be signed in to change notification settings - Fork 697
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.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please provide a binary for aarch64 + deb10 #8849
Comments
Hi! The cabal team is not able to produce these binaries, but @hasufell over at ghcup has built them (if these are what you need): haskell/ghcup-metadata@b703c55 |
BTW, is a GHC binary for exactly this platform produced by gitlab CI? If so, could you point me to a gitlab pipeline doing exactly that? |
Why? |
Official Docker images cannot contain unofficial binaries afaik, so we are somewhat dependent on the cabal project to provide those. How can we help to produce those, and where would we start? |
It appears this was a commit by @chreekat removing aarch64 linux: 0ea1001 The rationale was
At the time of the commit, this was already fixed in GHCup. See the changelog: https://github.com/haskell/ghcup-hs/blob/master/CHANGELOG.md#01191----2023-2-19 And the ticket: haskell/ghcup-hs#762 Further, the second part of the rationale doesn't make sense to me. You should be able to install the deb10 GHC on deb11. It seems I wasn't consulted on the PR either. |
Looks like the path to resolution is clearer now. |
My mistake, that was an oversight. I was just trying to get CI to green and forgot to double back on some of the issues I ran into. I'm surprised to hear it was already fixed in GHCUp, though. The CI script just basically runs |
Can I bring up again, that we should have a mailinglist for these kinds of issues? Currently you have to sift through various GitHub notifications, potentially some IRC/Matrix/Telegram chats... we should really have a mailing list with the interested CI related parties involved to keep everyone up to date what's happening across the whole GitHub:haskell ecosystem. |
Yes there is considerable overhead. |
I'm surprised too. The bootstrap script was updated in time: haskell/ghcup-hs@ea6c8d3 The ghcup release CI shows that deb10 was used to build: https://github.com/haskell/ghcup-hs/actions/runs/4254450877/jobs/7400717833 GHCup knows only Tier 1 platforms. So everything like that is a bug that I'll fix next weekend. |
Maybe I should run an apt-get update or something? I re-enabled aarch64-deb10 and aarch64-deb11 jobs, and sure enough the same thing happens: |
deb11 seems to be faring better — it's at least compiling Cabal now [edit: it has completed successfully]. https://gitlab.haskell.org/haskell/cabal/-/jobs/1404273. I hadn't considered that "there is no GHC release for aarch64-deb11" wouldn't be a blocker. |
Doing an update && upgrade with apt-get doesn't help. Installing the system requirements doesn't help, either (although it does install missing packages...) Unrelated: in Debian 11, installing the listed system requirements fails with |
Almost missed this message. I will see about getting a mailing list created. (There is an existing ghc-devops group, but its charter was explicitly "only ghc", which is not what we want.) |
Yes the GHC DevOps Group was an endearing experiment but clearly we need to think our operations and infrastructure at the scale of the Haskell project now. |
@chreekat I found the problem and will fix it tonight |
In debian 11, libffi6 is not listed as a system requirement: The source of truth is the boostrap script at the moment (invoking |
aarch64-linux-deb10 is back on the menu, e.g. https://downloads.haskell.org/cabal/cabal-install-3.10.2.0/cabal-install-3.10.2.0-aarch64-linux-deb10.tar.xz. Anything else we should do as followup? Closing in the meanwhile. |
It seems that the list of official binaries does currently not include a build for aarch64 on deb10. Adding this build would allow us to publish a new Docker image with GHC 9.6 and cabal-install 3.10.
See also: haskell/docker-haskell#102
The text was updated successfully, but these errors were encountered: