From mboxrd@z Thu Jan 1 00:00:00 1970 From: Charles Wilson To: Egor Duda Cc: cygwin@sources.redhat.com Subject: Re: make -mno-win32 the gcc default? Date: Thu, 11 Jan 2001 00:14:00 -0000 Message-id: <3A5D6B3D.48C2077F@ece.gatech.edu> 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> X-SW-Source: 2001-01/msg00511.html 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: CFLAGS="...." LDFLAGS="....." ./configure and if it were me, I *know* I'd forget to add "-mno-win32" every time. However, I hardly ever mess with "CC" or "CXX". Therefore, those variables are "safe" -- they won't be accidentally overridden. But that's just my tendencies. I'm sure other people have their own. --Chuck -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple