Unfortunately, this has broken mingw x-compilation for me: i686-pc-mingw32-g++ -DHAVE_CONFIG_H -I. -I../../src/Include -I../.. -I../../src -I/usr/i686-pc-mingw32/sys-root/mingw/include -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions --param=ssp-buffer-size=4 -mms-bitfields -D_REENTRANT -MT ATCVoice.o -MD -MP -MF .deps/ATCVoice.Tpo -c -o ATCVoice.o ATCVoice.cxx ATCVoice.cxx:42: error: expected unqualified-id before '<<' token make[2]: *** [ATCVoice.o] Error 1 make[2]: Leaving directory `/home/stefan/flightgear/flightgear/src/ATCDCL' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/stefan/flightgear/flightgear/src' make: *** [all-recursive] Error 1
Thanks, Stefan 2009/10/26, Erik Hofman <[email protected]>: > Csaba Halász wrote: >> On Mon, Oct 26, 2009 at 10:08 AM, James Turner <[email protected]> wrote: >>> >>> For these kind of fixes, I'd much rather you committed them straight >>> away to CVS, because it's easy for anyone to look at a single NaN fix >>> (or whatever) and convince themselves it's correct - or raise an >>> objection. When many trivial fixes are combined like this, the odds of >>> someone reading through the whole diff is going to be lower. >> >> I can't commit anything to cvs, so that's out of the question. And I >> hope I will never need to because we finally get rid of CVS :) >> Gitorious commits provide the relevant changes separately. See here: >> http://gitorious.org/~jester/fg/jesters-clone/commits/nan-fixes Each >> commit can be clicked and you get the relevant diff, such as >> http://gitorious.org/~jester/fg/jesters-clone/commit/99373b02c2e8d09a780de2e4c4b2b175437a05b6 >> >> But I have offered diffs, just say if you want a particular one :) I >> have attached the one for ATCVoice. > > This patch has been committed. Thanks, it was due time. > > Erik > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Flightgear-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
