From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: GHC/Stack build failures on i686
Date: Wed, 28 Jul 2021 08:31:59 +0200 [thread overview]
Message-ID: <20210728063159.F7BnGcMOZ5QuYPqskoFZ0Ftk2Qb3lim2ygSPXM5fBcM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32221@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/32221#issuecomment-888049344
Comment:
```
02:43 <Solid> ahesford, q66: well that's not good...
02:46 <Solid> apparently this is an issue with lukko and one has to compile cabal with `-ofd-locking`
02:47 <Solid> meaning we'd probably need to re-build cabal and patch in the respective json template ( https://github.com/haskell/cabal/blob/master/bootstrap/linux-8.10.4.json#L183 ) (they now also have a template for 8.10.4, so we can get rid of the patch for 8.10.1 and just use that)
02:48 <Solid> ghcup already seems to distributive this alternative bindist ( https://gitlab.haskell.org/haskell/ghcup-hs/-/commit/7e0f839ff8f91cb7cfc78eaa57782bc1af30dc4b ) and it seems to work
02:48 <Solid> (I'm writing this here because I'm really swamped with work for the next few weeks and so I don't think I'll have the time to actually build and test this; sorry!)
```
next prev parent reply other threads:[~2021-07-28 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 20:27 [ISSUE] " ahesford
2021-07-28 5:04 ` ericonr
2021-07-28 6:31 ` ericonr [this message]
2021-07-28 7:20 ` slotThe
2021-07-28 12:51 ` [ISSUE] [CLOSED] " leahneukirchen
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=20210728063159.F7BnGcMOZ5QuYPqskoFZ0Ftk2Qb3lim2ygSPXM5fBcM@z \
--to=ericonr@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).