[Mingw-w64-public] Custom toolchain build with gcc-4.4.5 (2010-09-14)

2010-09-14 Thread Ozkan Sezer
I updated my custom w32/w64 native and cross-compiler build with gcc-4.4 with several backports and fixes from mainstream, and put them under the mingw-w64 sf.net file release system under the subdirectories: - Toolchain sources -> Personal Builds, - Toolchains targetting Win32 -> Personal Builds

Re: [Mingw-w64-public] Problem with QtWebKit

2010-09-14 Thread NightStrike
On Sun, Aug 22, 2010 at 7:30 AM, Ruben Van Boxem wrote: > > > 2010/8/10 Ruben Van Boxem >>> >>> I still don't know of the errors you are getting but from what you say I >>> gather that they are because of some recent changes it your sources. >> >> Well, I got an update on the issue: beta2 (dated

Re: [Mingw-w64-public] w32 snapshot 20100902 (darwin) is failing in tree_mem_ref_addr, at tree-ssa-address.c:278

2010-09-14 Thread NightStrike
Yes, please report the ICE to GCC, and feel free to add nightstrike@@gmail.com to the CC list of the PR They will want preprocessed source. On Thu, Sep 9, 2010 at 8:44 PM, Luis Lavena wrote: > Hello, > > using the automated snapshots for darwin > (mingw-w32-bin_i686-darwin_20100902.tar.bz2) > >

Re: [Mingw-w64-public] ntddk.h

2010-09-14 Thread Alon Bar-Lev
On Tue, Sep 14, 2010 at 4:49 PM, Ozkan Sezer wrote: > On Tue, Sep 14, 2010 at 5:41 PM, Alon Bar-Lev wrote: >> Hi, >> >> When compiling this simple source: >> --- >> #include >> #include >> --- >> I get tones of errors of redefinitions winnt.h and ddk/ntddk.h. > > You aren't supposed to include

Re: [Mingw-w64-public] ntddk.h

2010-09-14 Thread Ozkan Sezer
On Tue, Sep 14, 2010 at 5:41 PM, Alon Bar-Lev wrote: > Hi, > > When compiling this simple source: > --- > #include > #include > --- > I get tones of errors of redefinitions winnt.h and ddk/ntddk.h. You aren't supposed to include those together: ntddk.h includes ntdef.h which includes necessary

[Mingw-w64-public] ntddk.h

2010-09-14 Thread Alon Bar-Lev
Hi, When compiling this simple source: --- #include #include --- I get tones of errors of redefinitions winnt.h and ddk/ntddk.h. Should it be possible? I am using stable branch. I am actually trying to make winpcap compile... this is the most problematic issue. Alon. ---

Re: [Mingw-w64-public] GCC stage1 lto broken?

2010-09-14 Thread Ruben Van Boxem
2010/9/14 Ruben Van Boxem > 2010/9/14 Teemu Nätkinniemi > > I am currently stopped by: >> >> Creating library file: ./shlib/libgcc_s.a.tmp >> lto1.exe: error: bad value (core2) for -mtls-dialect= switch >> lto-wrapper: M:\Development\msys\home\Ruben\mingw64\build\gcc\gcc\xgcc.exe >> returned 1 e

Re: [Mingw-w64-public] GCC stage1 lto broken?

2010-09-14 Thread Ruben Van Boxem
2010/9/14 Teemu Nätkinniemi > I am currently stopped by: > > Creating library file: ./shlib/libgcc_s.a.tmp > lto1.exe: error: bad value (core2) for -mtls-dialect= switch > lto-wrapper: M:\Development\msys\home\Ruben\mingw64\build\gcc\gcc\xgcc.exe > returned 1 exit status > collect2: lto-wrapper r

Re: [Mingw-w64-public] GCC stage1 lto broken?

2010-09-14 Thread Teemu Nätkinniemi
I am currently stopped by: Creating library file: ./shlib/libgcc_s.a.tmp lto1.exe: error: bad value (core2) for -mtls-dialect= switch lto-wrapper: M:\Development\msys\home\Ruben\mingw64\build\gcc\gcc\xgcc.exe returned 1 exit status collect2: lto-wrapper returned 1 exit status How about specifyin

Re: [Mingw-w64-public] GCC stage1 lto broken?

2010-09-14 Thread Ruben Van Boxem
2010/9/12 JonY > > I have no idea how to actually debug lto. > Neither do I, but I have an update to my progress: I have built a 4.6 GCC using the latest mingw-w64 autobuild (without lto), and this fresh compiler can do lto, so I can continue my search. I am currently stopped by: > Creating li

Re: [Mingw-w64-public] building GCC myself from MSYS

2010-09-14 Thread Ruben Van Boxem
2010/9/14 John E. / TDM > > This is correct. TDM64 GCC 4.5.1 is patched to remove a leading underscore > from the names of the _alloca and __chkstk symbols, in order for them to be > exported from both the 64-bit and 32-bit versions of libgcc with the same > export rule (there is another patch in