Comment 8 for bug 759357

Sammie S. Taunton (diemuzi) wrote :

Decided to try upgrading GCC to the newest version and the same problems exist. But at the same time version 0.18 is still compiling just fine without issues. Simply because I do not understand your last comment, can you explain how/what you mean by disable the warnings to error code? Once I understand I'll give it a try.

[root@pacman64 ~]$ gcc -v
Using built-in specs.
Target: x86_64-unknown-linux-gnu
Configured with: /build/src/gcc-4.6-20110415/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl= --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --enable-gnu-unique-object --enable-linker-build-id --with-ppl --enable-cloog-backend=isl --enable-lto --enable-gold --enable-ld=default --enable-plugin --disable-multilib --disable-libstdcxx-pch --enable-checking=release
Thread model: posix
gcc version 4.6.0 20110415 (prerelease) (GCC)