From: Jon Turney <jon.turney@dronecode.org.uk>
To: William Hu <purplearmadillo77@proton.me>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Cygport Bug: "find: No such file" Errors When Packaging
Date: Sat, 17 Sep 2022 13:27:37 +0100 [thread overview]
Message-ID: <9e4a2d4b-528e-f19f-048f-cc07f824c47a@dronecode.org.uk> (raw)
In-Reply-To: <gm6yTD7Gz9l0cL6auP3wvndqKLXAvtXT_Uayft3CSl19jNcuGzwV5vtpqSMnSDHW-VIkUxK7rWXXneA_Q2FOvq4tBwzf7SyFI3_9TYP0ZGs=@proton.me>
On 15/09/2022 20:38, William Hu via Cygwin-apps wrote:
> Hello,
>
[...]
>
> Cygport checks one more time to make sure mldir exists in the package being built
> (this second check is why those errors are hard to trigger on a non-OCaml package)
> and then calls `find` on both ${D}${mldir} and ${mldir}. Of course, since the
> *real* /usr/lib/ocaml won't exist if OCaml isn't installed on your actual system
> when you build it, find will output an error when run on those two directories.
>
> Two ways to fix this would be to either remove the ${mldir} argument from find or
> test if ${mldir} exists and set it to the empty string if it doesn't. The second
> would likely preserve compatibility if there exist packages that depend on find
> searching both directories. The buggy test was added in
> <https://github.com/cygwin/cygport/commit/7d24eb71bdd91e2a368739728dbd522ddd4faaac>.
> Does anyone else have any insights or suggestions or does the above fix sound
> reasonable?
I think just dropping ${mldir} would prevent cygport from detecting the
dependencies of an ocaml library (other ocaml libraries, or ocaml
itself?), but the second alternative sounds acceptable.
Patches welcome, as always :)
next prev parent reply other threads:[~2022-09-17 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 19:38 William Hu
2022-09-17 12:27 ` Jon Turney [this message]
2022-09-17 21:14 ` William Hu
2022-09-18 13:17 ` Jon Turney
2022-10-02 20:49 ` 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=9e4a2d4b-528e-f19f-048f-cc07f824c47a@dronecode.org.uk \
--to=jon.turney@dronecode.org.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).