make -mno-win32 the gcc default?

Christopher Faylor cgf@redhat.com
Thu Jan 11 12:58:00 GMT 2001


On Thu, Jan 11, 2001 at 03:29:44PM -0500, Earnie Boyd wrote:
>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.

Yes.  I think that Earnie is right here.

cgf

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



More information about the Cygwin mailing list