From: ftrvxmtrx <ftrvxmtrx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] Update to GHC 9.0.2/Stackage LTS-19.0
Date: Wed, 23 Mar 2022 21:40:31 +0100 [thread overview]
Message-ID: <20220323204031.yrSVD0W7QGvzUyK7W3jnjWTz7di2H-Yujls7709PpU4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36292@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
New comment by ftrvxmtrx on void-packages repository
https://github.com/void-linux/void-packages/pull/36292#issuecomment-1076791182
Comment:
@slotThe I condensed the changes required to get it build on aarch64 and aarch64-musl to one commit: https://github.com/ftrvxmtrx/void-packages/commit/401a299740c47d8f6e1d1d55fb8a09fb38dc08c4
I think it'd be best to get that change into your PR somehow, without merging the PR I made for ghc-8.*. Feel free to cut/rebase parts you might already have in your local tree.
* [distfile for aarch64](https://ftrv.se/_/void/ghc-9.0.2/ghc-9.0.2-aarch64-void-linux.tar.xz)
* [distfile for aarch64-musl](https://ftrv.se/_/void/ghc-9.0.2/ghc-9.0.2-aarch64-void-linux-musl.tar.xz)
I've built `ghc-bin` for both, now building `ghc` which is going to take some time.
next prev parent reply other threads:[~2022-03-23 20:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 7:20 [PR PATCH] " slotThe
2022-03-23 20:31 ` ftrvxmtrx
2022-03-23 20:40 ` ftrvxmtrx [this message]
2022-03-24 10:51 ` [PR PATCH] [Updated] " slotThe
2022-03-24 10:51 ` slotThe
2022-03-24 11:34 ` slotThe
2022-03-24 13:37 ` slotThe
2022-03-24 23:05 ` ftrvxmtrx
2022-03-25 12:11 ` [PR PATCH] [Updated] " slotThe
2022-03-25 13:14 ` slotThe
2022-03-25 13:15 ` [PR PATCH] [Updated] " slotThe
2022-03-25 13:44 ` slotThe
2022-03-26 16:43 ` ftrvxmtrx
2022-03-28 16:15 ` ftrvxmtrx
2022-03-30 13:44 ` ftrvxmtrx
2022-03-31 17:15 ` [PR PATCH] [Updated] " slotThe
2022-03-31 17:16 ` slotThe
2022-04-03 11:51 ` ftrvxmtrx
2022-04-23 5:51 ` slotThe
2022-04-23 5:51 ` slotThe
2022-04-28 0:47 ` [PR PATCH] [Closed]: " q66
2022-04-28 0:47 ` q66
2022-05-03 10:12 ` Piraty
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=20220323204031.yrSVD0W7QGvzUyK7W3jnjWTz7di2H-Yujls7709PpU4@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).