From: mnabid <mnabid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: ibus-avro-1.1
Date: Thu, 26 Mar 2020 10:34:12 +0100 [thread overview]
Message-ID: <20200326093412.b0Earu3sG14sX159FrfRaxWUal8f9d1sFA4xw4mAazU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20370@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
New comment by mnabid on void-packages repository
https://github.com/void-linux/void-packages/pull/20370#issuecomment-604324625
Comment:
`i686` build failed due to missing shlib `libffi.so.6` (looks like issue #20336 isn't solved yet for cross builds).
But why **libffi-3.3.tar.gz** can't be fetched in `aarch64` and `aarch64-musl` builds? I can fetch it manually with no issues. Any help?
next parent reply other threads:[~2020-03-26 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20370@inbox.vuxu.org>
2020-03-26 9:34 ` mnabid [this message]
2020-03-31 10:49 ` mnabid
2020-04-05 10:39 ` mnabid
2020-04-08 6:34 ` mnabid
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=20200326093412.b0Earu3sG14sX159FrfRaxWUal8f9d1sFA4xw4mAazU@z \
--to=mnabid@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).