On Aug 28 04:36, Dave Korn wrote: > On 18/08/2011 15:33, Corinna Vinschen wrote: > > > If I try that with Yaakov's 4.5.3 cross compilers, then __STRICT_ANSI__ > > is not defined with -std=c__0x, unless I also specify `-ansi' on the > > command line. However, there's a weird warning: > > > > $ i686-pc-cygwin-g++ -std=c++0x -dM -E - < /dev/null | grep ANSI > > cc1: warning: command line option "-std=c++0x" is valid for C++/ObjC++ > > but not for C > > > > Well, sure, that's why I called g++, not gcc... > > Ah, but without a file extension, it doesn't know what language you're > feeding it; for some reason -std doesn't imply -x. Compare: > > > $ g++-4 -std=c++0x -dM -E - < /dev/null | grep ANSI > > cc1: warning: command line option "-std=c++0x" is valid for C++/ObjC++ but > > not f > > or C > > > > $ g++-4 -std=c++0x -x c++ -dM -E - < /dev/null | grep ANSI > > #define __STRICT_ANSI__ 1
Uh, thanks. I didn't even know the -x flag. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
