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: René Berber
Subject: Re: [Mingw-cross-env-list] Did unsupported/win32-g++-cross/qmake.conf change?
Date: Sat, 24 Sep 2011 10:29:00 -0500
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.0

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.

Should I complain upstream then?  I guess so.

But what is going on here? who is D.L. Miles and why is he changing the
win32-g++-cross files?  Aren't these files an addition made by this project?
-- 
René Berber




reply via email to

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