Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <3A5E17B8.FB338BAC@yahoo.com>
Date: Thu, 11 Jan 2001 15:29:44 -0500
From: Earnie Boyd <earnie_boyd@yahoo.com>
Reply-To: "cygwin@cygwin.com" <cygwin@cygwin.com>
MIME-Version: 1.0
To: Charles Wilson <cwilson@ece.gatech.edu>
CC: Egor Duda <cygwin@cygwin.com>
Subject: Re: make -mno-win32 the gcc default?
References: <20010110163107.A4979@redhat.com>
		 <3A5CDA12.B7533F6C@ece.gatech.edu> <20010110170527.B21342@volta.certicom.com>
		 <3A5CDEA3.CAB59B71@ece.gatech.edu> <171329197110.20010111103208@logos-m.ru> <3A5D6B3D.48C2077F@ece.gatech.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Charles Wilson wrote:
> 
> Egor Duda wrote:
> >
> > Hi!
> >
> > Thursday, 11 January, 2001 Charles Wilson cwilson@ece.gatech.edu wrote:
> >
> > CW> Sure.  'export CC="gcc -mwin32"' and 'export CXX="g++ -mwin32"' in your
> > CW> .bashrc
> >
> > perhaps  we  should put
> > 'export  CC="gcc -mno-win32"' and 'export CXX="g++ -mno-win32"' in our
> > .bashrc's and live with it for some time before making it default?
> >
> > BTW, shouldn't it be
> > 'export  CFLAGS="-mno-win32"' and 'export CXXFLAGS="-mno-win32"' ?
> 
> Yeah, you're probably right.  But lots of times I'll do this:
> 

No, he's wrong, IMO.  CC, CXX are the correct variables to set.  The
reason is that CFLAGS and CXXFLAGS should be used for optimization and
flags that are architecture independent while the architecture dependent
flags should be passed with the CC, CXX variables.  This allows the
configure script to use the architecture dependent flags in it's checks
for what's available.  Otherwise, you might misconfigure the package.

Cheers,
Earnie.

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


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple