unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Thomas Klausner <tk@giga.or.at>
To: 29940@debbugs.gnu.org
Subject: bug#29940: Acknowledgement (guile-2.2.3 does not work pax mprotect)
Date: Mon, 8 Jan 2018 11:42:22 +0100	[thread overview]
Message-ID: <20180108104222.a5g7fnjbvqspesmm@danbala> (raw)
In-Reply-To: <handler.29940.B.151488425022993.ack@debbugs.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 357 bytes --]

The attached patch is a workaround: we can mark the guile binary to
not use the PAX mprotect feature using paxctl +m. On Linux, paxctl has
different flags, so I wrapped it in an "if", and it uses knowledge of
libtool internals, so it is not a good idea to integrate this patch
as-is.

Better would be of course to make guile work with PAX mprotect.
 Thomas

[-- Attachment #2: patch-libguile_Makefile.in --]
[-- Type: text/plain, Size: 599 bytes --]

$NetBSD: patch-libguile_Makefile.in,v 1.1 2018/01/08 10:39:45 wiz Exp $

Fix build on NetBSD>=8.

--- libguile/Makefile.in.orig	2017-11-06 09:12:56.000000000 +0000
+++ libguile/Makefile.in
@@ -2444,6 +2444,8 @@ clean-noinstPROGRAMS:
 guile$(EXEEXT): $(guile_OBJECTS) $(guile_DEPENDENCIES) $(EXTRA_guile_DEPENDENCIES) 
 	@rm -f guile$(EXEEXT)
 	$(AM_V_CCLD)$(guile_LINK) $(guile_OBJECTS) $(guile_LDADD) $(LIBS)
+	if [ `uname -s` = "NetBSD" ]; then paxctl +m .libs/guile$(EXEEXT); fi
+
 install-binSCRIPTS: $(bin_SCRIPTS)
 	@$(NORMAL_INSTALL)
 	@list='$(bin_SCRIPTS)'; test -n "$(bindir)" || list=; \

  parent reply	other threads:[~2018-01-08 10:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02  9:10 bug#29940: guile-2.2.3 does not work pax mprotect Thomas Klausner
     [not found] ` <sfid-+20180102-101108-+008.55-1@spamfilter.osbf.lua>
     [not found]   ` <handler.29940.B.151488425022993.ack@debbugs.gnu.org>
2018-01-08 10:42     ` Thomas Klausner [this message]
2018-01-08 22:52       ` bug#29940: Acknowledgement (guile-2.2.3 does not work pax mprotect) Thomas Klausner

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=20180108104222.a5g7fnjbvqspesmm@danbala \
    --to=tk@giga.or.at \
    --cc=29940@debbugs.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).