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: <3C42E3CB.C876A7A1@yahoo.com>
Date: Mon, 14 Jan 2002 08:57:31 -0500
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jon Leichter <jonleichter AT mediaone DOT net>
CC: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>, hschwentner AT yahoo DOT com,
   cygwin AT cygwin DOT com
Subject: Re: Compiling apps to Mingw32 with cygwin
References: <CIENIMJIOHKBPJEFFFOBMEKPCBAA DOT jonleichter AT mediaone DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Jon Leichter wrote:
> 
> 
> > > 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.
> > >

You're not going to switch the tools from cp to copy or rm to del by
doing as I suggest.  You would have to buggle (use unnecessary
conditions) the Makefile.in to do that.

> > > 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
> 
> Grrr... This makes one start believing that Earnie's method is more correct.

Uhm, yes, that would be the reason not to emulate the cross build.

> I suppose the right answer to this question is: use whichever method seems
> to work best for the project that you're working on. If they both work the
> same, then use your favorite one.
> 

Note, that I think that a _true_ cross build is the more correct way to
build for MinGW using Cygwin.  However, `gcc -mno-cygwin' isn't a _true_
cross compiler so you shouldn't treat it as one.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
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/