Re: [patch] gcc4 fixes
Brian Dessent wrote: Christopher Faylor wrote: While this might help to avoid... something, I'm seriously wondering what's wrong with this expression. Why does each new version of gcc add new incompatibilities? Well, it might actually be a gcc bug. Here I admit to using a snapshot verion of gcc and not the 4.0 release, primarily because I had read of bug reports e.g. KDE blacklisting 4.0 entirely in their build scripts due to compiler problems. So who knows, maybe I should try with a release build. $ g++-4 -v Using built-in specs. Target: i686-pc-cygwin Configured with: ../gcc-4.1-20050501/configure --verbose --prefix=/usr/local --exec-prefix=/usr/local --sysconfdir=/etc --libdir=/usr/local/lib --libexecdir=/usr/local/lib --mandir=/usr/local/man --infodir=/usr/local/info --program-suffix=-4 --enable-languages=c,c++ --disable-nls --without-included-gettext --with-system-zlib --enable-interpreter --enable-threads=posix --enable-sjlj-exceptions --disable-version-specific-runtime-libs --disable-win32-registry Thread model: posix gcc version 4.1.0 20050501 (experimental) I want to switch using --disable-sjlj-exceptions with gcc-4.x, could you try to build with this instead of --enabl-sjlj? Gerrit -- =^..^=
Re: [patch] gcc4 fixes
Christopher Faylor wrote: Go ahead and check these in but please use GNU formatting conventions, i.e., it's (char *) NULL, not (char *)NULL. Actually, isn't just NULL sufficient? I must have had C++ on the mind, thinking that the cast was necessary. Sorry but no. This is a workaround. We need to fix the actual problem. Certainly. I fully admit I have no real idea what the 'actual' problem is yet. Brian
Re: [patch] gcc4 fixes
On Tue, May 17, 2005 at 06:15:08PM -0700, Brian Dessent wrote: Christopher Faylor wrote: Go ahead and check these in but please use GNU formatting conventions, i.e., it's (char *) NULL, not (char *)NULL. Actually, isn't just NULL sufficient? I must have had C++ on the mind, thinking that the cast was necessary. Sorry but no. This is a workaround. We need to fix the actual problem. Certainly. I fully admit I have no real idea what the 'actual' problem is yet. I don't either, obviously. Nice job tracking it down, regardless. cgf
