X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.6 required=5.0 	tests=BAYES_50,J_CHICKENPOX_38
X-Spam-Check-By: sourceware.org
Date: Thu, 29 Jan 2009 21:00:53 +1300
From: Danny Smith <dannysmith AT clear DOT net DOT nz>
Subject: Re: RFD: cygwin + *native* MinGW compiler
To: Cygwin <cygwin AT cygwin DOT com>
Message-id: <BEBA87DEFCC94625AFD40845D6E627FE@THOMAS>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Note-from-DJ: This may be spam

At:
http://www.cygwin.com/ml/cygwin/2009-01/msg00848.html

Charles Wilson said:
Greg said
>>
>>I use '--build=3Di686-pc-mingw32 --host=3Di686-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=3Dmingw32 --host=3Dmingw32 --target=3Dmingw32"=
=20
when building gcc are
1) I have, perhaps mistakenly, assumed that "--build=3D" 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 u=
nderstand
symlinks.  "--build=3Dcygwin32"  would suggest that the native gcc understa=
nds symlinks.
Ditto for my binutil and gdb apps which do not depend on cygwin.
3) specifying "--host=3Dmingw32 --target=3Dmingw32" usually works just fine=
 too (within a
cygwin bash shell), for most projects, as long as there are no assumptions =
about symlinks.

4) "--build=3Dmingw32 --host=3Dmingw32 --target=3Dmingw32"  always seemed t=
o be a natural way to
do a bootstrap.

I don't set any special environment variables before I "bash ./config.sh" f=
rom a DOS
prompt (my everday path just put C:/mingw/bin in front of C:/cygwin/bin) an=
d 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/