From: Simon South <simon@simonsouth.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 51241@debbugs.gnu.org
Subject: [bug#51241] [PATCH 0/1] gnu: ragel: Fix build of knot on aarch64-linux.
Date: Mon, 20 Dec 2021 17:57:32 -0500 [thread overview]
Message-ID: <874k72yjdv.fsf@simonsouth.net> (raw)
In-Reply-To: <8735momdml.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Sun, 19 Dec 2021 23:30:26 +0100")
Ludovic Courtès <ludo@gnu.org> writes:
> Could you check whether this is still needed on current master,
> ca. 9b38d9b3b34edb55f7f42b72a611b39e5164cf9f?
Unfortunately yes; Knot is still failing two "yparser" tests in master
(2c469f04a3be) on AArch64.
> ‘guix refresh -l ragel’ reports 5K dependents, so we’d need to apply the
> patch conditionally for aarch64 in a phase, or something along these
> lines.
I can submit a new patch with this change. Or would it make more sense
to apply the existing patch to the version-1.4.0 branch, since it's
fixing an issue in master?
--
Simon South
simon@simonsouth.net
next prev parent reply other threads:[~2021-12-20 22:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 17:04 [bug#51241] [PATCH 0/1] gnu: ragel: Fix build of knot on aarch64-linux Simon South
2021-10-16 17:06 ` [bug#51241] [PATCH 1/1] " Simon South
2021-10-16 17:42 ` [bug#51241] [PATCH 0/1] " Tobias Geerinckx-Rice via Guix-patches via
2021-10-16 20:09 ` Simon South
2021-10-16 21:37 ` Tobias Geerinckx-Rice via Guix-patches via
2021-11-12 20:44 ` [bug#51241] [PATCH v2 " Simon South
2021-11-12 20:44 ` [bug#51241] [PATCH v2 1/1] " Simon South
2021-12-19 22:30 ` [bug#51241] [PATCH 0/1] " Ludovic Courtès
2021-12-20 22:57 ` Simon South [this message]
2021-12-21 9:12 ` Ludovic Courtès
2021-12-29 17:46 ` Simon South
2021-12-29 17:46 ` [bug#51241] [PATCH 1/1] " Simon South
2021-12-31 17:29 ` bug#51241: " Ludovic Courtès
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=874k72yjdv.fsf@simonsouth.net \
--to=simon@simonsouth.net \
--cc=51241@debbugs.gnu.org \
--cc=ludo@gnu.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).