unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
* pax mprotect and guile build process
@ 2020-11-08 16:13 Greg Troxel
  0 siblings, 0 replies; only message in thread
From: Greg Troxel @ 2020-11-08 16:13 UTC (permalink / raw)
  To: guile-devel

[-- 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 --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2020-11-08 16:13 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-08 16:13 pax mprotect and guile build process Greg Troxel

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).