From: Jon Turney <jon.turney@dronecode.org.uk>
To: William Hu <purplearmadillo77@proton.me>,
David Allsopp <David.Allsopp@cl.cam.ac.uk>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITA] ocaml 4.14.0
Date: Sat, 16 Jul 2022 15:22:21 +0100 [thread overview]
Message-ID: <ad3816cb-6ddd-c8d8-0b91-9722f1ba351f@dronecode.org.uk> (raw)
In-Reply-To: <e60e3f2e19ea4c778aa66ab98e292b1d@metastack.com>
On 13/07/2022 16:41, David Allsopp wrote:
>
>> 3) Interesting - on my machine, the camlheader[di] files had the .exe
>> extensions. I did some digging around and found the files are *built*
>> without the .exe suffix, and even *initially installed* without the .exe
>> suffix, but ultimately come out with the .exe suffix. I ran cyport in
>> debug mode and apparently the files are being renamed with the suffix
>> post-install:
>>
>> + case "${exe##*/}" in
>> + mv usr/lib/ocaml/camlheaderd usr/lib/ocaml/camlheaderd.exe
>> + exe+=.exe
>>
>> and did a little more digging and I think these lines in cygport are the
>> cause:
>> https://github.com/cygwin/cygport/blob/096f27644bd3b28f29d7522e816bebd327c
>> f24cb/lib/src_postinst.cygpart#L1010
Yeah, that seems plausible, but I'm not clear why we are seeing
different behaviour...
>> On the topic of "testing more thoroughly", I attempted to use
>> ocamlc to compile a simple program and it fails with "Cannot find
>> file camlheader" but works when I remove the ".exe", so it seems
>> that the presence of the .exe suffixes breaks the compiler. Is
>> there a way to prevent cygport from adding it?
>
> The camlheader files are data files and definitely mustn't be
> installed with a .exe extension (nor do they need to be executable).
I'm confused here: /usr/lib/ocaml/camlheaderd[di] look like executables
(according to file etc.)
If they genuinely aren't, then perhaps they shouldn't have execute
permission (which is I think what is causing them to be caught by that
piece of code in cygport...)
next prev parent reply other threads:[~2022-07-16 14:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 2:03 William Hu
2022-07-04 17:03 ` Jon Turney
2022-07-05 0:42 ` William Hu
2022-07-05 19:44 ` Jon Turney
2022-07-13 2:56 ` William Hu
2022-07-13 15:41 ` David Allsopp
2022-07-14 3:36 ` William Hu
2022-07-14 14:56 ` David Allsopp
2022-07-15 3:20 ` William Hu
2022-07-16 14:22 ` Jon Turney [this message]
2022-07-23 16:38 ` William Hu
2022-07-31 14:52 ` Jon Turney
2022-08-07 2:26 ` William Hu
2022-08-23 20:00 ` David Allsopp
2022-08-24 9:20 ` Corinna Vinschen
2022-08-24 9:28 ` David Allsopp
2022-08-24 9:28 ` David Allsopp
2022-08-24 10:04 ` Corinna Vinschen
2022-07-16 14:05 ` Jon Turney
2022-07-17 20:56 ` William Hu
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=ad3816cb-6ddd-c8d8-0b91-9722f1ba351f@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=David.Allsopp@cl.cam.ac.uk \
--cc=cygwin-apps@cygwin.com \
--cc=purplearmadillo77@proton.me \
/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).