From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libtool: update to 2.4.7.
Date: Thu, 17 Nov 2022 22:28:32 +0100 [thread overview]
Message-ID: <20221117212832.nte-o3876MaW5QJY5oWSXCHHY21GQ4LDMtCwIHxpmKI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39313@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/39313#issuecomment-1319227647
Comment:
it seems there's yet another cross-compilation issue with libtool:
if i use the packaged libtool to compile ntl, then it fails,
as previously reported, while if i natively compile libtool first,
then I can successfully use it to build ntl (on aarch64),
including passing tests.
next prev parent reply other threads:[~2022-11-17 21:28 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 11:29 [PR PATCH] Libtool oreo639
2022-09-16 12:02 ` [PR PATCH] [Updated] libtool: update to 2.4.7 oreo639
2022-09-16 12:09 ` oreo639
2022-09-16 12:11 ` oreo639
2022-09-16 12:16 ` oreo639
2022-09-16 12:34 ` oreo639
2022-09-16 12:35 ` oreo639
2022-09-16 13:04 ` oreo639
2022-09-16 14:28 ` oreo639
2022-09-16 14:31 ` oreo639
2022-09-16 14:45 ` oreo639
2022-09-16 14:57 ` oreo639
2022-09-16 17:38 ` [PR REVIEW] " paper42
2022-09-16 17:38 ` paper42
2022-09-16 17:50 ` dkwo
2022-09-16 22:40 ` [PR REVIEW] " oreo639
2022-09-16 22:40 ` oreo639
2022-09-16 22:42 ` oreo639
2022-09-16 22:43 ` oreo639
2022-09-16 22:43 ` [PR PATCH] [Updated] " oreo639
2022-10-05 18:02 ` dkwo
2022-10-10 13:56 ` dkwo
2022-11-16 14:18 ` dkwo
2022-11-16 17:23 ` oreo639
2022-11-16 17:24 ` oreo639
2022-11-16 17:26 ` oreo639
2022-11-16 17:28 ` [PR PATCH] [Updated] " oreo639
2022-11-16 17:32 ` oreo639
2022-11-16 17:33 ` oreo639
2022-11-16 17:35 ` oreo639
2022-11-16 20:53 ` oreo639
2022-11-16 20:57 ` oreo639
2022-11-16 21:04 ` oreo639
2022-11-16 21:26 ` [PR PATCH] [Updated] " oreo639
2022-11-16 21:29 ` oreo639
2022-11-16 21:58 ` [PR PATCH] [Updated] " oreo639
2022-11-16 23:36 ` oreo639
2022-11-16 23:45 ` oreo639
2022-11-16 23:58 ` oreo639
2022-11-17 0:24 ` oreo639
2022-11-17 0:31 ` oreo639
2022-11-17 0:40 ` oreo639
2022-11-17 1:53 ` oreo639
2022-11-17 17:46 ` oreo639
2022-11-17 17:56 ` oreo639
2022-11-17 20:15 ` [PR PATCH] [Merged]: " paper42
2022-11-17 21:28 ` dkwo [this message]
2022-11-17 23:20 ` oreo639
2022-11-18 4:39 ` oreo639
2022-11-18 5:01 ` oreo639
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=20221117212832.nte-o3876MaW5QJY5oWSXCHHY21GQ4LDMtCwIHxpmKI@z \
--to=dkwo@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).