From: Simon South <simon@simonsouth.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41363-done@debbugs.gnu.org
Subject: [bug#41363] knot-resolver: Enable reloading of policy files (add lua-cqueues)
Date: Thu, 25 Jun 2020 10:18:28 -0400 [thread overview]
Message-ID: <87zh8rcjpn.fsf@simonsouth.net> (raw)
In-Reply-To: <87pn9nsaox.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 25 Jun 2020 12:26:38 +0200")
Ludovic Courtès <ludo@gnu.org> writes:
> Should we disable the Lua dependency on AArch64?
I'd leave it as-is (despite the confusing error message), since you can
work around the issue on AArch64 with a rebuilt kernel configured to use
39-bit virtual addresses rather than the default 48.
Plus I'm most of the way towards updated patches that use more recent
versions of cqueues and luaossl, which avoids the problem
altogether. This is still on my to-do list though not a priority at the
moment.
--
Simon South
simon@simonsouth.net
next prev parent reply other threads:[~2020-06-25 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 14:46 [bug#41363] knot-resolver: Enable reloading of policy files (add lua-cqueues) Simon South
2020-05-17 16:09 ` [bug#41363] [PATCH 1/3] gnu: Add lua-ossl Simon South
2020-05-17 16:09 ` [bug#41363] [PATCH 2/3] gnu: Add lua-cqueues Simon South
2020-05-17 16:09 ` [bug#41363] [PATCH 3/3] gnu: knot-resolver: Enable automatic reloading of policy files Simon South
2020-05-18 12:32 ` [bug#41363] [PATCH 1/3] gnu: Add lua-ossl Simon South
2020-05-19 10:25 ` [bug#41363] knot-resolver: Enable reloading of policy files (add lua-cqueues) Simon South
2020-05-29 19:36 ` Simon South
2020-06-17 10:02 ` Ludovic Courtès
2020-06-25 10:26 ` bug#41363: " Ludovic Courtès
2020-06-25 14:18 ` Simon South [this message]
2020-06-25 21:06 ` [bug#41363] " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh8rcjpn.fsf@simonsouth.net \
--to=simon@simonsouth.net \
--cc=41363-done@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.