From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-3.8.1_1: broken, unresolvable shlib `libffi.so.6'
Date: Wed, 25 Mar 2020 07:12:38 +0100 [thread overview]
Message-ID: <20200325061238.j4J7wjy0Vjr6z8idOOSfezpDLD6TkcMYn90pbuiaZ-w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20336@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/20336#issuecomment-603660088
Comment:
Ok, second try resulted in a much larger tarball with all files it seems:
[https://distfiles.voidlinux.de/ghc-8.6.5-x86_64-void-linux-musl.tar.xz](https://distfiles.voidlinux.de/ghc-8.6.5-x86_64-void-linux-musl.tar.xz)
Checksum e335578cf199588dbfd5a3c678a4fc0b0d44ec83771a902a01e510b993b3e01e
Building `ghc-bin-8.6.5_2` for `x86_64-musl` worked for me.
I wonder if we should add a `build_option="bindist"` to the `ghc` template to make it easier in the future.
I also wonder if and how I could create a `ghc-bin` for `i686-musl`.
Who's going to update `ghc-bin` or should we wait for someone to put in on `alpha.de.repo.voidlinux.org/distfiles` ?
next prev parent reply other threads:[~2020-03-25 6:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 6:15 [ISSUE] " mnabid
2020-03-24 6:25 ` pullmoll
2020-03-24 6:30 ` mnabid
2020-03-25 1:24 ` q66
2020-03-25 2:03 ` pullmoll
2020-03-25 2:57 ` pullmoll
2020-03-25 3:09 ` q66
2020-03-25 3:10 ` q66
2020-03-25 3:16 ` pullmoll
2020-03-25 3:18 ` pullmoll
2020-03-25 3:18 ` pullmoll
2020-03-25 3:19 ` q66
2020-03-25 3:19 ` pullmoll
2020-03-25 4:49 ` pullmoll
2020-03-25 5:08 ` pullmoll
2020-03-25 6:11 ` pullmoll
2020-03-25 6:12 ` pullmoll [this message]
2020-03-25 9:21 ` pullmoll
2020-03-25 14:08 ` Duncaen
2020-03-25 14:08 ` q66
2020-03-25 22:39 ` Francesco149
2020-03-25 22:41 ` q66
2020-03-25 22:41 ` [ISSUE] [CLOSED] " q66
2020-03-26 9:40 ` mnabid
2020-03-26 11:02 ` Duncaen
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=20200325061238.j4J7wjy0Vjr6z8idOOSfezpDLD6TkcMYn90pbuiaZ-w@z \
--to=pullmoll@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).