From: Greg Troxel <gdt@lexort.com>
To: guile-devel@gnu.org
Subject: pax mprotect and guile build process
Date: Sun, 08 Nov 2020 11:13:29 -0500 [thread overview]
Message-ID: <rmitutzn7x2.fsf@s1.lexort.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
(I think I may have reported this earlier but I can't find it.)
NetBSD runs with pax mprotect by default. Guile's JIT has trouble with
this, due to the nature of JIT.
In pkgsrc, we have:
NOT_MPROTECT_SAFE+= ${GUILE_PREFIX}/bin/guile
to do "paxctl +m" for guile as installed. However, during the build,
the guile that has been built is used, and that guile fails. So this
needs to be hoisted to guile's build procedure, not just a patch
afterwards.
I can't find any paxctl in the guile build procedure.
I would expect this problem to occur on all systems that have pax
mprotect on by default, and would also expect most systems to be doing
that these days. So it doesn't make sense to me that I am the only one
seeing this.
So I wonder how this generally works on GNU/Linux systems?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
reply other threads:[~2020-11-08 16:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=rmitutzn7x2.fsf@s1.lexort.com \
--to=gdt@lexort.com \
--cc=guile-devel@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.
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).