On Sun, May 8, 2011 at 17:47, Ruben Van Boxem wrote:
> I have released an update to my 4.6.1 prerelease toolchain.
> 1. linking code with lto using the "-flto" switch crashes ld. Trunk
> crashes, 2.21 as well, 2.20 complains about not being compiled with
> "--enable-plugins", but can't be compiled
Hi Ruben!
On Sun, May 8, 2011 at 2:15 PM, Ruben Van Boxem wrote:
> Op 8 mei 2011 16:21 schreef "K. Frank" het volgende:
>> Hello Ruben!
>> ...
>> (I''ve taken the liberty of cross-posting this to the Qt list, because I
>> have a question about Qt; see below.)
>>
>> On Sun, May 8, 2011 at 5:47 AM,
Op 8 mei 2011 16:21 schreef "K. Frank" het volgende:
>
> Hello Ruben!
>
> Thanks!
>
> (I''ve taken the liberty of cross-posting this to the Qt list, because I
> have a question about Qt; see below.)
>
> On Sun, May 8, 2011 at 5:47 AM, Ruben Van Boxem
> wrote:
> > I have released an update to my 4
Hello Ruben!
Thanks!
(I''ve taken the liberty of cross-posting this to the Qt list, because I
have a question about Qt; see below.)
On Sun, May 8, 2011 at 5:47 AM, Ruben Van Boxem
wrote:
> I have released an update to my 4.6.1 prerelease toolchain.
> ...
> There is both a 32-bit and 64-bit buil
Hi,
I have a mingw64 4.6.0 cross-compiler (20100414) which I'm in the process of
phasing out, as it doesn't comply with MSVC standards regarding the
decoration of library symbols.
With that compiler, I inserted into both mingw/include/_mingw.h and
x86_64-w64-mingw32/include/_mingw.h the follow
I have released an update to my 4.6.1 prerelease toolchain.
I have used:
- mingw-w64 trunk
- GCC 4.6.1 branch
- binutils trunk (2.21.51)
- GDB 7.2 release
- make 3.82
- latest GMP, MPFR, MPC, PPL, CLooG-isl
The toolchain should be capable of compiling/linking C, C++, fortran,
Objective-C, a
On 5/8/2011 06:39, Jonas noLastName wrote:
>
>> Can you tell us which mingw64 compiler you used?
>>
>
> x86_64-w64-mingw32-gcc.exe (GCC)
> 4.5.2Using:https://mingw-w64.svn.sourceforge.net/svnroot/mingw-w64/branches/releases/v1.0revision
> 4166Need anything else just ask.
> I have send another m