From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>, Andrea Corallo <akrl@sdf.org>
Cc: 50818@debbugs.gnu.org
Subject: bug#50818: 28.0.50; .eln files need to be executable on Cygwin
Date: Mon, 27 Sep 2021 14:52:15 -0400 [thread overview]
Message-ID: <dc887f32-4e60-905d-0ef5-4b5964456738@cornell.edu> (raw)
In-Reply-To: <bec3f21d-48d5-1b0d-8a3f-369f9f7331a8@cornell.edu>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
On 9/26/2021 12:57 PM, Ken Brown wrote:
> On 9/26/2021 12:04 PM, Eli Zaretskii wrote:
>> Please define a new INSTALL_ELN macro for that purpose.
>
> OK. But I'd like to hear first (maybe from Andrea?) whether there's a reason
> for this to be Cygwin-specific, and whether INSTALL_DATA is in fact typically
> used for installing libraries on other platforms.
I decide to go ahead with a Cygwin-specific patch (attached). If Andrea or
someone else decides this would be good for all platforms, they can do that later.
OK to push?
Ken
[-- Attachment #2: 0001-Make-.eln-files-executable-on-Cygwin.patch --]
[-- Type: text/plain, Size: 1557 bytes --]
From 6bec21243d20df015875ee8576bc722224480acb Mon Sep 17 00:00:00 2001
From: Ken Brown <kbrown@cornell.edu>
Date: Mon, 27 Sep 2021 14:46:41 -0400
Subject: [PATCH] Make .eln files executable on Cygwin
* Makefile.in (INSTALL_ELN): New variable, equal to $(INSTALL) on
Cygwin and $(INSTALL_DATA) on other platforms.
(install-eln): Use INSTALL_ELN instead of INSTALL_DATA.
(Bug#50818)
---
Makefile.in | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/Makefile.in b/Makefile.in
index 235b707673..5fc1edc7a3 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -285,10 +285,16 @@ use_gamedir=
# not use an absolute path. So we must take care to always run
# INSTALL-type commands from the directory containing the Makefile.
# This explains (I think) the cd thisdir seen in several install rules.
+SYSTEM_TYPE = @SYSTEM_TYPE@
INSTALL = @INSTALL@
INSTALL_PROGRAM = @INSTALL_PROGRAM@
INSTALL_DATA = @INSTALL_DATA@
INSTALL_INFO = @INSTALL_INFO@
+ifeq ($(SYSTEM_TYPE),cygwin)
+ INSTALL_ELN = $(INSTALL)
+else
+ INSTALL_ELN = $(INSTALL_DATA)
+endif
# By default, we uphold the dignity of our programs.
INSTALL_STRIP =
MKDIR_P = @MKDIR_P@
@@ -791,7 +797,7 @@ install-eln:
ifeq ($(HAVE_NATIVE_COMP),yes)
umask 022 ; \
find native-lisp -type d -exec $(MKDIR_P) "$(ELN_DESTDIR){}" \; ; \
- find native-lisp -type f -exec ${INSTALL_DATA} "{}" "$(ELN_DESTDIR){}" \;
+ find native-lisp -type f -exec ${INSTALL_ELN} "{}" "$(ELN_DESTDIR){}" \;
endif
### Build Emacs and install it, stripping binaries while installing them.
--
2.33.0
next prev parent reply other threads:[~2021-09-27 18:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 15:03 bug#50818: 28.0.50; .eln files need to be executable on Cygwin Ken Brown
2021-09-26 16:04 ` Eli Zaretskii
2021-09-26 16:57 ` Ken Brown
2021-09-27 18:52 ` Ken Brown [this message]
2021-09-27 19:12 ` Eli Zaretskii
2021-09-27 19:26 ` Ken Brown
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=dc887f32-4e60-905d-0ef5-4b5964456738@cornell.edu \
--to=kbrown@cornell.edu \
--cc=50818@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@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 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).