From: Danny Smith <dannysmith@clear.net.nz>
To: Cygwin <cygwin@cygwin.com>
Subject: Re: RFD: cygwin + *native* MinGW compiler
Date: Thu, 29 Jan 2009 09:52:00 -0000 [thread overview]
Message-ID: <BEBA87DEFCC94625AFD40845D6E627FE@THOMAS> (raw)
At:
http://www.cygwin.com/ml/cygwin/2009-01/msg00848.html
Charles Wilson said:
Greg said
>>
>>I use '--build=i686-pc-mingw32 --host=i686-pc-mingw32'. Here:
>> http://lists.gnu.org/archive/html/libtool-patches/2009-01/msg00193.html
>>you say that's lying to 'configure', but you also observe that
>>I'm in excellent company. I'd be dismayed if that broke.
>
>Well, as I point out above: it's already very fragile, and.requires a
>great deal of careful setup to get it to work "correctly" (if generating
>DLLs with the wrong name can be considered "correct").
>
>I wouldn't want to gratuitously break this usage, but I am leaning
>towards endorsing the suggestion that it's bad to lie to your toolchain.
>However, if you REALLY want to do so, and assume all the risk of
>breakage/failure/hairloss/heartburn, then...set these [*] environment
>variables before you ./configure, and then cross your fingers...
The reasons I use "--build=mingw32 --host=mingw32 --target=mingw32"
when building gcc are
1) I have, perhaps mistakenly, assumed that "--build=" referred to the OS of the compiler,
not the ethnicity of the shell.
2) my build gcc is a mingw32 gcc, and unlike a cygwin-hosted gcc, doesn't understand
symlinks. "--build=cygwin32" would suggest that the native gcc understands symlinks.
Ditto for my binutil and gdb apps which do not depend on cygwin.
3) specifying "--host=mingw32 --target=mingw32" usually works just fine too (within a
cygwin bash shell), for most projects, as long as there are no assumptions about symlinks.
4) "--build=mingw32 --host=mingw32 --target=mingw32" always seemed to be a natural way to
do a bootstrap.
I don't set any special environment variables before I "bash ./config.sh" from a DOS
prompt (my everday path just put C:/mingw/bin in front of C:/cygwin/bin) and I don't cross
my fingers because I know it has worked for 10 years or so.
Danny
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2009-01-29 8:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 9:52 Danny Smith [this message]
2009-01-29 12:29 ` Charles Wilson
2009-01-29 15:13 ` Charles Wilson
-- strict thread matches above, loose matches on Subject: below --
2009-01-28 4:38 Charles Wilson
2009-01-28 5:29 ` Christopher Faylor
2009-01-28 6:14 ` Warren Young
2009-01-28 6:55 ` Greg Chicares
2009-01-28 7:18 ` Charles Wilson
2009-01-28 9:05 ` Yaakov (Cygwin/X)
2009-01-28 11:10 ` Charles Wilson
2009-01-28 11:21 ` Yaakov (Cygwin/X)
2009-01-28 15:19 ` Christopher Faylor
2009-01-28 23:08 ` Greg Chicares
2009-01-29 9:44 ` Charles Wilson
2009-02-11 2:34 ` Greg Chicares
2009-01-28 15:15 ` Ralph Hempel
2009-01-28 15:18 ` Vincent R.
2009-01-28 15:26 ` Christopher Faylor
2009-01-28 16:08 ` Roger Wells
2009-01-28 16:40 ` Claude Sylvain
2009-01-28 17:22 ` Reini Urban
2009-01-28 23:47 ` Kai Raphahn
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=BEBA87DEFCC94625AFD40845D6E627FE@THOMAS \
--to=dannysmith@clear.net.nz \
--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).