Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <08ec01c19c71$3dd521a0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Jon Leichter" <jonleichter AT mediaone DOT net>,
   "Earnie Boyd" <earnie_boyd AT yahoo DOT com>
Cc: <hschwentner AT yahoo DOT com>, <cygwin AT cygwin DOT com>
References: <CIENIMJIOHKBPJEFFFOBEEKHCBAA DOT jonleichter AT mediaone DOT net>
Subject: Re: Compiling apps to Mingw32 with cygwin
Date: Mon, 14 Jan 2002 07:31:11 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime: 13 Jan 2002 20:31:05.0364 (UTC) FILETIME=[39899540:01C19C71]



----- Original Message -----
From: "Jon Leichter" <jonleichter AT mediaone DOT net>


> First off... thanks again to both Robert and Earnie for taking part in
this
> discussion. I appreciate it a lot.
>
> Recapping once again...
>
> Robert says to use:
>
> $ ./configure --host=i686-pc-mingw32 --build=i686-pc-cygwin
>
> (no need to set CC if i686-pc-mingw32-gcc exists)
>
> Earnie says to use:
>
> $ ./configure --host=i686-pc-mingw32 --build=i686-pc-mingw32
>
> (still need to explicitly set CC)

Both invocations need to explicitly set CC - because of older configure
scripts in the first case.

> Using Robert's invocation WOULD put configure in cross-compile mode.
But
> since using Cygwin GCC to generate MinGW is ALMOST like a
cross-compile, it
> will work out ok. In fact, one compelling reason to use Robert's
method is
> because one wants the configure script to use the correct build tools,
e.g.
> cp instead of copy, rm instead of del, etc. I tend to agree that the
build
> environment IS Cygwin for this very reason.
>
> So here's a question. If configure is put into cross-compile mode
(with
> Robert's method), then wouldn't it be the case that configure would
NOT
> execute test binaries? If so, does that hurt the configuration process
in
> any way? Is this a problem?

Errgle. It _can_ affect the configure process. Say for instance, squid.
Squid uses test binaries to determine socket sizes, maximum fd limits
and the like, which it can't do during a cross compile run, so the cross
compiler (individual) has to provide those on the command line.
Cross-compiling certainly reduces the 'magic' detection that can take
place.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/