This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin64 build recipe (was: Re: cygwin64 process substitution: known bug?)
- From: "Gregory M. Turner" <gmt at malth dot us>
- To: cygwin at cygwin dot com
- Date: Tue, 09 Apr 2013 05:23:36 -0700
- Subject: Re: cygwin64 build recipe (was: Re: cygwin64 process substitution: known bug?)
- References: <5161DCD1 dot 7040002 at malth dot us> <20130408081044 dot GB10199 at calimero dot vinschen dot de> <20130408093850 dot GA12628 at calimero dot vinschen dot de> <51632E49 dot 5070500 at malth dot us> <20130409092338 dot GK10126 at calimero dot vinschen dot de>
On Tue, Apr 9, 2013 at 2:23 AM, Corinna Vinschen wrote:
No, not really. You can do that, and I still use the Linux cross
compiler to build Cygwin, but we don't really *have* to bootstrap
$ cygport cygwin.cygport download prep compile install package
$ cygport cygwin.cygport download allmostall
That should do it.
Before I got this reply I tried native 64->64 ./configure && make &&
make install (roughly speaking) out-of-tree against cvs and... it worked
like a champ! One quirk -- by default it builds as
x86_64-unknown-cygwin, whereas iirc the 32-bit equivalent builds as
*-pc-cygwin... after supplying host/build/target configure arguments and
/usr prefix, everything seemed fully cooked at a glance.
Doing it the cygport way sounds even better, though, since then I get
setup64.exe-based deployment, autorebase, and whatever postinstall
magic, avoiding the old make install / crash / make install ritual.
< party-hat / confetti emoticon >
hoping against hope he managed to post this successfully exactly one time
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple