Re: [Mingw-w64-public] Debugging Clang 3.2 rubenvb build

2013-03-22 Thread Ruben Van Boxem
2013/3/8 Abir Basak > If I want to debug an executable created with clang 3.2 rubenvb build, it > shows DW_FORM_strp pointing outside .debug_str section > The gdb version comes with the build > GNU gdb (rubenvb-4.6.3-2-release) 7.5.50.20121228-cvs > > Is there any way I can debug an application

Re: [Mingw-w64-public] [Interest] Compiling Qt (4 or 5) with "-std=c++11"

2013-03-22 Thread K. Frank
Hi Ruben! Great. Thanks for clearing things up. On Fri, Mar 22, 2013 at 10:09 AM, Ruben Van Boxem wrote: > 2013/3/22 K. Frank > >> Hello Ruben! >> ... > No, I never implied such a thing. I was talking about x86 only. There is no > dw2 for x64 and in all likelihood never will be. >> >> Let me c

Re: [Mingw-w64-public] What's a good 64-bit native build to upgrade to?

2013-03-22 Thread Ruben Van Boxem
2013/3/22 niXman > 2013/3/22 K. Frank: > > Hello List (and Ruben)! > > > > I am thinking about upgrading my compiler (and various libraries I use). > > I am currently using one of Ruben's 64-bit 4.7 builds. > > > > I'm looking for additional c++11 support, keeping, of course, support for > > std:

Re: [Mingw-w64-public] [Interest] Compiling Qt (4 or 5) with "-std=c++11"

2013-03-22 Thread Ruben Van Boxem
2013/3/22 K. Frank > Hello Ruben! > > On Fri, Mar 22, 2013 at 6:22 AM, Ruben Van Boxem > wrote: > > 2013/3/22 JonY > >> > >> On 3/22/2013 11:26, K. Frank wrote: > >> > > >> >> If you're interested in a binary compatibility topic that might > affect > >> >> you -- > >> >> and since you so kindly

Re: [Mingw-w64-public] What's a good 64-bit native build to upgrade to?

2013-03-22 Thread niXman
2013/3/22 K. Frank: > Hello List (and Ruben)! > > I am thinking about upgrading my compiler (and various libraries I use). > I am currently using one of Ruben's 64-bit 4.7 builds. > > I'm looking for additional c++11 support, keeping, of course, support for > std::thread. I imagine that 4.8 is the

[Mingw-w64-public] What's a good 64-bit native build to upgrade to?

2013-03-22 Thread K. Frank
Hello List (and Ruben)! I am thinking about upgrading my compiler (and various libraries I use). I am currently using one of Ruben's 64-bit 4.7 builds. I'm looking for additional c++11 support, keeping, of course, support for std::thread. I imagine that 4.8 is the way to go. My wish list: 6

Re: [Mingw-w64-public] [Interest] Compiling Qt (4 or 5) with "-std=c++11"

2013-03-22 Thread K. Frank
Hello Ruben! On Fri, Mar 22, 2013 at 6:22 AM, Ruben Van Boxem wrote: > 2013/3/22 JonY >> >> On 3/22/2013 11:26, K. Frank wrote: >> > >> >> If you're interested in a binary compatibility topic that might affect >> >> you -- >> >> and since you so kindly brought the mingw community in -- be carefu

Re: [Mingw-w64-public] [Interest] Compiling Qt (4 or 5) with "-std=c++11"

2013-03-22 Thread JonY
On 3/22/2013 18:22, Ruben Van Boxem wrote: >>> >>> Yes, another compatibility issue. I've been using the dwarf2 version. >>> (But there are sjlj advocates out there.) >>> >> >> Yes, DW2 is quite frankly broken on Windows, since you'll never be able >> to recompile system libraries to be able to th

Re: [Mingw-w64-public] [Interest] Compiling Qt (4 or 5) with "-std=c++11"

2013-03-22 Thread Ruben Van Boxem
2013/3/22 JonY > On 3/22/2013 11:26, K. Frank wrote: > > > >> If you're interested in a binary compatibility topic that might affect > you -- > >> and since you so kindly brought the mingw community in -- be careful > about the > >> C++ exception model from your mingw compiler. They are > binary-

Re: [Mingw-w64-public] [Interest] Compiling Qt (4 or 5) with "-std=c++11"

2013-03-22 Thread Kai Tietz
2013/3/22 JonY : > Yes, DW2 is quite frankly broken on Windows, since you'll never be able > to recompile system libraries to be able to throw through it (or 3rd > party code built with MSVC). It is even more broken on win64. Well, to be more correct here. For x64 (there is no win64 btw) there is

Re: [Mingw-w64-public] [Interest] Compiling Qt (4 or 5) with "-std=c++11"

2013-03-22 Thread JonY
On 3/22/2013 11:26, K. Frank wrote: > >> If you're interested in a binary compatibility topic that might affect you -- >> and since you so kindly brought the mingw community in -- be careful about >> the >> C++ exception model from your mingw compiler. They are binary-incompatible >> with one ano