mingw-cross-env-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] Re: GCC 4.5 (was URL problems)


From: Mark Brand
Subject: Re: [Mingw-cross-env-list] Re: GCC 4.5 (was URL problems)
Date: Fri, 30 Apr 2010 17:16:59 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.2pre) Gecko/20100308 SUSE/3.1b1-6.3 Thunderbird/3.1b1


I did a quick diff of the qt logs, and there seems to be three differences:

1) In some places GCC4.4.0 uses -fexceptions -mthreads -frtti
                    where GCC4.5 uses -fno-exceptions -fno-rtti
(without -mthreads)

Great idea. It inspired me to do the same experiment. I don't see the difference you describe in 1). That's a bit puzzling. Could this be because we are working on different platforms? I am using 64-bit opensuse Linux. The detection of rtti support is added to the Qt configure script by a mingw-cross-env patch. I'm curious about what the rtti detection does on your system with gcc 4.4 and 4.5. Here the test is positive as expected in both cases. For gcc 4.5:

rtti auto-detection... ()
gmake[2]: Entering directory `/home/brand/projects/mingw-cross-env.dev/x/tmp-qt/qt-everywhere-opensource-src-4.6.2/config.tests/unix/rtti' i686-pc-mingw32-g++ -c -isystem /home/brand/projects/mingw-cross-env.dev/x/usr/i686-pc-mingw32/include -pipe -frtti -O2 -Wall -fno-exceptions -fno-rtti -DUNICODE -DQT_TABLET -DQT_SESSIONMANAGER -DQT_NO_DIRECT3D -DQT_NO_CODECS -DQT_NEEDS_QMAIN -DQT_NO_DYNAMIC_CAST -I"." -I"../../../mkspecs/win32-g++" -o rtti.o rtti.cpp i686-pc-mingw32-g++ -enable-stdcall-fixup -Wl,-enable-auto-import -Wl,-enable-runtime-pseudo-reloc -Wl,-s -Wl,-subsystem,windows -o rtti.exe rtti.o gmake[2]: Leaving directory `/home/brand/projects/mingw-cross-env.dev/x/tmp-qt/qt-everywhere-opensource-src-4.6.2/config.tests/unix/rtti'
rtti enabled.


2) GCC 4.5 has slightly different warning strings
3) GCC 4.5 terminates earlier with errors


Yes, I see this do. Nothing looks problematic.


regards,

Mark




reply via email to

[Prev in Thread] Current Thread [Next in Thread]