From: Maxime Devos <maximedevos@telenet.be>
To: muradm <mail@muradm.net>
Cc: "\(" <paren@disroot.org>, 56872@debbugs.gnu.org
Subject: [bug#56872] [PATCH v2] gnu: mu: Update to 1.8.7.
Date: Tue, 2 Aug 2022 22:19:03 +0200 [thread overview]
Message-ID: <c13a46ee-5aeb-bee2-75c4-fb7a05de3f78@telenet.be> (raw)
In-Reply-To: <87fsiemmf9.fsf@muradm.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 674 bytes --]
On 02-08-2022 22:13, muradm wrote:
> From below error I see that it is pth package failing to build.
> Most likely there are others that are not getting built.
> Does it mean that it was never built before mu-1.8.7?
> Does it mean that we sould restrict mu-1.8.7 by platform?
>
It fails to cross-compile to aarch64-linux (--target), but it compiles
fine natively (--system without --target), so I don't think adjusting
'supported-systems' is necessary. Rather, it seems to me that pth'
configure script should eventually be tweaked to support
aarch64-linux-gnu not only when compiling natively, but also when
cross-compiling.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-08-02 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 13:11 [bug#56872] [PATCH] gnu: mu: Update to 1.8.7 muradm
2022-08-01 13:41 ` [bug#56872] [PATCH v2] " muradm
2022-08-02 16:25 ` Maxime Devos
2022-08-02 19:03 ` muradm
2022-08-02 19:14 ` ( via Guix-patches via
2022-08-02 19:27 ` muradm
2022-08-02 19:59 ` Maxime Devos
2022-08-02 20:13 ` muradm
2022-08-02 20:19 ` Maxime Devos [this message]
2022-08-02 19:53 ` Maxime Devos
2022-08-01 13:44 ` [bug#56872] [PATCH v3] " muradm
2022-08-01 14:05 ` bug#56872: [PATCH] " Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c13a46ee-5aeb-bee2-75c4-fb7a05de3f78@telenet.be \
--to=maximedevos@telenet.be \
--cc=56872@debbugs.gnu.org \
--cc=mail@muradm.net \
--cc=paren@disroot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).