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: Sun, 26 Sep 2021 12:57:24 -0400 [thread overview]
Message-ID: <bec3f21d-48d5-1b0d-8a3f-369f9f7331a8@cornell.edu> (raw)
In-Reply-To: <83a6jznx17.fsf@gnu.org>
On 9/26/2021 12:04 PM, Eli Zaretskii wrote:
>> From: Ken Brown <kbrown@cornell.edu>
>> Date: Sun, 26 Sep 2021 11:03:53 -0400
>>
>> An installed emacs built with native compilation won't start on Cygwin because
>> the executable permissions have been removed from the .eln files. This is done
>> in the install-eln target of the top-level Makefile.in, which installs the .eln
>> files with 644 permissions even though they were created with executable
>> permissions.
>
> Is what we do different from any other package the installs DLLs?
Yes. DLLs are always installed with 755 permissions. Packages that install
DLLs typically use libtool, which just does the right thing. I can't recall
offhand seeing a hand-written Makefile rule for installing a DLL, but I assume
it would use INSTALL or INSTALL_PROGRAM rather than INSTALL_DATA. It seems
strange to me to see INSTALL_DATA used for installing a library, but I'm not
really familiar with what's typically done on GNU/Linux, for example
>> Would it hurt anything on other platforms if the .eln files were installed with
>> 755 permissions? If so, I can submit a patch that does this just on Cygwin.
>
> 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.
Ken
next prev parent reply other threads:[~2021-09-26 16:57 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 [this message]
2021-09-27 18:52 ` Ken Brown
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bec3f21d-48d5-1b0d-8a3f-369f9f7331a8@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.