[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Mingw-cross-env-list] Did unsupported/win32-g++-cross/qmake.conf ch
From: |
Mark Brand |
Subject: |
Re: [Mingw-cross-env-list] Did unsupported/win32-g++-cross/qmake.conf change? |
Date: |
Sat, 24 Sep 2011 09:47:07 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20110907 Thunderbird/6.0.2 |
On 09/23/2011 08:41 PM, René Berber wrote:
Hi,
Silly question, I know, of course it changed, the real question is why?
Last week I was seeing g++ using "-Wl,-enable-stdcall-fixup" and other
parameters for the linker, today they are not there.
I changed the Qt version this Monday (with 'hg pull -u', and rebuild Qt
and all its dependencies), so that caused this change.
Applications still build, but we're back to getting those annoying
messages about the linker guessing what we wanted to link.
Is this an upstream change?
Hi René,
These changes come from the regular win32-g++ Qt mkspec. Here is the commit:
commit 0c4ed66e87ef6f76d5b0d67905b587c31ad03a18
Author: Darryl L. Miles <address@hidden>
Date: Thu Mar 31 11:16:50 2011 +0200
Remove useless LFLAGS
These options were found to be no longer required for MinGW releases at
this time (they are also never valid for MinGW64 when building 64bit).
They actually never worked anyway, as the GNU toolchain linker option
"-enable-stdcall-fixup" actually means "-e" "nable-stdcall-fixup".
Merge-request: 1158
Reviewed-by: Oswald Buddenhagen <address@hidden>
diff --git a/mkspecs/win32-g++/qmake.conf b/mkspecs/win32-g++/qmake.conf
index 9f10f75..1469abd 100644
--- a/mkspecs/win32-g++/qmake.conf
+++ b/mkspecs/win32-g++/qmake.conf
@@ -52,7 +52,7 @@ QMAKE_RUN_CXX_IMP = $(CXX) -c $(CXXFLAGS)
$(INCPATH) -o $@ $<
QMAKE_LINK = g++
QMAKE_LINK_C = gcc
-QMAKE_LFLAGS = -Wl,-enable-stdcall-fixup
-Wl,-enable-auto-import -Wl,-enable-runtime-pseudo-reloc
+QMAKE_LFLAGS =
QMAKE_LFLAGS_EXCEPTIONS_ON = -mthreads
QMAKE_LFLAGS_EXCEPTIONS_OFF =
QMAKE_LFLAGS_RELEASE = -Wl,-s