From: ftrvxmtrx <ftrvxmtrx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: ghc, ghc-bin: add aarch64* support
Date: Wed, 06 Apr 2022 02:53:26 +0200 [thread overview]
Message-ID: <20220406005326.fJKKLThREDFqLLg5TLI119gntXcJeaienhPzMoAfDRU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36193@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
There's a closed pull request on the void-packages repository
ghc, ghc-bin: add aarch64* support
https://github.com/void-linux/void-packages/pull/36193
Description:
GHC uses llvm (specifically `opt` and `llc` executables) to build on aarch64, so that was added as a dependency.
All packages that depend on ghc were built and are available at a [repo I made with signed *.xbps files](https://ftrv.se/_/void/ghc-aarch64-musl) along with the [ghc bindist distfile](https://ftrv.se/_/void/ghc-aarch64-musl/ghc-8.10.7-aarch64-void-linux-musl.tar.xz) required by ghc-bin, which this change assumes is eventually uploaded to `alpha.de.repo.voidlinux.org`. I tested most of the packages, they all work as expected.
I can share the files in some other way if that's preferable.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (aarch64-musl, aarch64)
[ci skip]
prev parent reply other threads:[~2022-04-06 0:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 22:02 [PR PATCH] ghc, ghc-bin: add aarch64-musl support ftrvxmtrx
2022-03-21 17:06 ` [PR PATCH] [Updated] " ftrvxmtrx
2022-03-21 18:21 ` ghc, ghc-bin: add aarch64* support ftrvxmtrx
2022-04-06 0:53 ` ftrvxmtrx [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220406005326.fJKKLThREDFqLLg5TLI119gntXcJeaienhPzMoAfDRU@z \
--to=ftrvxmtrx@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).