From: Paul Eggert <eggert@cs.ucla.edu>
To: Thomas Klausner <wiz@NetBSD.org>
Cc: 23371@debbugs.gnu.org
Subject: bug#23371: emacs: paxctl usage on NetBSD
Date: Wed, 27 Apr 2016 12:38:53 -0700 [thread overview]
Message-ID: <3f6aba54-4f40-817c-24f9-942b033d2289@cs.ucla.edu> (raw)
In-Reply-To: <20160427155442.GN7662@danbala.tuwien.ac.at>
On 04/27/2016 08:54 AM, Thomas Klausner wrote:
>> configure.ac says
>> that paxctl is used only when the operating system is GNU/Linux, unless one
>> manually configures by setting PAXCTL in the environment or using a
>> PAXCTL=/some/path argument to 'configure'.
> That's true, but src/Makefile.in ignores that:
> PAXCTL_if_present = $(or $(PAXCTL),: paxctl)
I guess I'm still not following. On non-GNU/Linux hosts, $(PAXCTL)
should be empty because paxctl is not searched for, so PAXCTL_if_present
should be ': paxctl', i.e., a no-op shell command. And yet you reported
that your build used 'paxctl -zex' and 'paxctl -r'. Perhaps your build
was actually using the no-ops ': paxctl -zex' and ': paxctl -r' and you
didn't notice the colons? That is, perhaps you replaced ': paxctl -zex'
(with a prefix colon) with 'paxctl +a' (without the colon)?
>
> My version is attached (I added some more paxctl's for the symlinks
> when the original version didn't work.) I hope I didn't break it.
Did it work with your version?
If so, does 'ln' and/or 'mv' remove the mark placed on an executable by
'paxctl +a'? and if that happens, how does 'make install' avoid removing
the mark in the installed Emacs?
If not, then I'm afraid I'm lost.
Also, I noticed that you removed the indenting on some of the 'ifeq'
lines in src/Makefile.in; why was that necessary?
next prev parent reply other threads:[~2016-04-27 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 12:09 bug#23371: emacs: paxctl usage on NetBSD Thomas Klausner
2016-04-26 0:09 ` Paul Eggert
2016-04-27 15:54 ` Thomas Klausner
2016-04-27 19:38 ` Paul Eggert [this message]
2016-04-27 22:50 ` Thomas Klausner
2016-04-27 23:08 ` Paul Eggert
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f6aba54-4f40-817c-24f9-942b033d2289@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=23371@debbugs.gnu.org \
--cc=wiz@NetBSD.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/emacs.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).