From: DRC <dcommander@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: cygport does not automatically generate dependencies
Date: Fri, 12 Jun 2020 10:06:31 -0500 [thread overview]
Message-ID: <d163dbe3-327a-6e44-15ff-e319263fd4fb@users.sourceforge.net> (raw)
In-Reply-To: <b0792c3b-1db9-ac4a-d86e-c552816186c2@gmail.com>
On 6/12/20 4:29 AM, Marco Atzeri via Cygwin-apps wrote:
>> That only works when you don't cross-compile and you didn't say whether
>> you are or not.
>
> and if you have installed the cygwin packages for the build
> and you are not using your own hand installed one.
>
> cygport --debug <cygport_file> deps
>
> will be very verbose on the dependencies check
I figured it out. Apparently the cygport script requires .exe files to
have execute permissions in order to check dependencies on them, and for
whatever reason, when running my build on a shared network drive, those
files weren't created with the correct permissions. I ran the build on
a local drive, and it works properly now.
prev parent reply other threads:[~2020-06-12 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 5:44 DRC
2020-06-12 7:03 ` ASSI
2020-06-12 9:29 ` Marco Atzeri
2020-06-12 15:06 ` DRC [this message]
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=d163dbe3-327a-6e44-15ff-e319263fd4fb@users.sourceforge.net \
--to=dcommander@users.sourceforge.net \
--cc=cygwin-apps@cygwin.com \
/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).