From: Yaakov Selkowitz <yselkowitz@gmail.com>
To: cygwin@cygwin.com
Subject: Re: compiling coreutils with cygport
Date: Mon, 16 Jul 2012 10:29:00 -0000 [thread overview]
Message-ID: <5003ED0D.7040209@gmail.com> (raw)
In-Reply-To: <CAMkU=1yRPm7vu30taP6Y0xNy3BRZxVOYUAL_aMCo794SSbGb6Q@mail.gmail.com>
On 2012-07-13 16:25, Jeff Janes wrote:
> If I use setup.exe to download the src for coreutils (just by checking
> the "Src?" checkbox in the gui) , and then use cygport to build it, it
> fails. The reason it fails seems to be that ginstall.exe does not
> have the proper manifest file so windows refuses to execute it. This
> is the same error you get if you try to build coreutils downloaded
> from upstream gnu sources.
Right, cygport really isn't the problem here.
> cygport coreutils-8.15-1.cygport prep compile
> ....
> make[2]: Entering directory `/usr/src/coreutils-8.15-1/build/man'
> GEN install.1
> help2man: can't get `--help' info from install.td/install
> Makefile:1833: recipe for target `install.1' failed
> make[2]: *** [install.1] Error 126
This occurs because help2man runs ginstall to get its --help and
--version output, but UAC doesn't allow it because of its name (but
let's not go *there* again). This also would occur during make install,
where the in-tree ginstall is used as $(INSTALL).
cygport has for some time created .manifest files during postinstall,
which has taken care of UAC issues for end users. However, there is no
way for cygport to know what executables are being created during the
*build*, and then that they actually need to be run in the build tree
(most do not). That being said, adding this as a manual command for
cases like this is pretty easy.
Please try cygport git master together with adding the following line to
coreutils-*.cygport immediately *before* the cygmake command:
manifestize src/ginstall.exe
That WFM on W7.
(Eric: BTW, while I'm at it, there's an easier way to handle DIR_COLORS:
insinto /etc
doins $B/src/DIR_COLORS
make_etc_defaults /etc/DIR_COLORS
No custom postinstall/preremove necessary. :-)
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2012-07-16 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 21:25 Jeff Janes
2012-07-13 22:04 ` Eric Blake
2012-07-14 7:50 ` Corinna Vinschen
2012-07-14 7:54 ` Corinna Vinschen
2012-07-16 9:01 ` Yaakov (Cygwin/X)
2012-07-16 10:29 ` Yaakov Selkowitz [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=5003ED0D.7040209@gmail.com \
--to=yselkowitz@gmail.com \
--cc=cygwin@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).