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] Did unsupported/win32-g++-cross/qmake.conf ch


From: Tony Theodore
Subject: Re: [Mingw-cross-env-list] Did unsupported/win32-g++-cross/qmake.conf change?
Date: Sun, 25 Sep 2011 02:18:41 +1000

On 25 September 2011 01:29, René Berber <address@hidden> wrote:
> On 24 Sep 2011 09:47:07, Mark Brand wrote:
>
>> 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>
>
> I would say this is a bad joke, if it wasn't real.
>
> Why does D.L. Miles think that -enable-stdcall-fixup actually is a -e
> ...?  The documentation is clear:
> http://sourceware.org/binutils/docs-2.21/ld/Options.html#Options
> (section 2.1.1) but these guys probably don't read it.

Those flags should all have a double dash prefix, so he's probably
right in saying that they would be parsed as something useless.

This doesn't explain why your seeing a change in behaviour though - it
seems they would never have worked.

Cheers,

Tony



reply via email to

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