From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: RFD: cygwin + *native* MinGW compiler
Date: Wed, 28 Jan 2009 09:05:00 -0000 [thread overview]
Message-ID: <497FF7D0.3090505@users.sourceforge.net> (raw)
In-Reply-To: <497FED17.4040901@cwilson.fastmail.fm>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Charles Wilson wrote:
> This led to a suggestion that "--build=cygwin --host=mingw32" should
> always be interpreted as: mingw32-gcc is a cygwin-hosted cross compiler,
> NOT the native MinGW-project supported gcc (and if it IS the native
> MinGW one, expect breakage). I'm not sure such a sweeping statement is
> accurate, or wise -- will that assumption break people's exising
> (working) setups?
If you're talking about configure gcc with those flags, then wouldn't
that usually mean that you're cross-compiling a regular, native MinGW
compiler? If you want a cygwin-hosted MinGW cross-compiler, you should
be using "--build=cygwin --host=cygwin --target=mingw32". I would be
hesitant to change the usual meaning of build/host just for
Cygwin/MinGW; I don't think we need to add to the confusion that most
people have about Cygwin.
Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkl/99AACgkQpiWmPGlmQSPwWwCg2zTu9HT+7n9KllpstMDFMQSI
54kAoMO87bM+BuTptalxE3hHkP8uOYoU
=7GVr
-----END PGP SIGNATURE-----
--
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 prev parent reply other threads:[~2009-01-28 6:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
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) [this message]
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
2009-01-29 9:52 Danny Smith
2009-01-29 12:29 ` Charles Wilson
2009-01-29 15:13 ` Charles Wilson
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=497FF7D0.3090505@users.sourceforge.net \
--to=yselkowitz@users.sourceforge.net \
--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).