Re: [Mingw-w64-public] New Rubenvb GCC 4.8 std::thread enabled build

2013-04-02 Thread Baruch Burstein
Thank you all for your clear explanations! On Tue, Apr 2, 2013 at 3:23 PM, JonY wrote: > On 4/2/2013 20:05, Ruben Van Boxem wrote: > > If you want a static winpthreads but shared libgcc/libstdc++, you'll need > > to remove libwinpthread.dll.a from your toolchain directory. Your mileage > > may

Re: [Mingw-w64-public] New Rubenvb GCC 4.8 std::thread enabled build

2013-04-02 Thread JonY
On 4/2/2013 20:05, Ruben Van Boxem wrote: > If you want a static winpthreads but shared libgcc/libstdc++, you'll need > to remove libwinpthread.dll.a from your toolchain directory. Your mileage > may vary. Note my current builds only work with -static, I omitted the > known fix for this issue from

Re: [Mingw-w64-public] New Rubenvb GCC 4.8 std::thread enabled build

2013-04-02 Thread Ruben Van Boxem
2013/4/2 Baruch Burstein > Just to clarify that I understand the process: > The GCC implementation of and friends (part of the libc or libgcc > or libstdc++ or whatever the GCC standard library is called) really uses > pthread calls under the hood. Changing that would mean changing the code of >

Re: [Mingw-w64-public] New Rubenvb GCC 4.8 std::thread enabled build

2013-04-02 Thread Baruch Burstein
Just to clarify that I understand the process: The GCC implementation of and friends (part of the libc or libgcc or libstdc++ or whatever the GCC standard library is called) really uses pthread calls under the hood. Changing that would mean changing the code of the standard library implementation.

Re: [Mingw-w64-public] New Rubenvb GCC 4.8 std::thread enabled build

2013-04-02 Thread Ruben Van Boxem
Op 2 apr. 2013 11:51 schreef "Kai Tietz" het volgende: > > 2013/4/2 Ruben Van Boxem >> >> 2013/4/2 Baruch Burstein >>> >>> Can you explain the difference from your "regular" builds? Does std::thread not work with them? If I use std::thread, do I need to link/distribute any additional libraries?

Re: [Mingw-w64-public] New Rubenvb GCC 4.8 std::thread enabled build

2013-04-02 Thread Kai Tietz
2013/4/2 Ruben Van Boxem > 2013/4/2 Baruch Burstein > >> Can you explain the difference from your "regular" builds? Does >> std::thread not work with them? If I use std::thread, do I need to >> link/distribute any additional libraries? Or are there special licenses >> issues? >> In short: Why 2

Re: [Mingw-w64-public] New Rubenvb GCC 4.8 std::thread enabled build

2013-04-02 Thread Ruben Van Boxem
2013/4/2 Baruch Burstein > Can you explain the difference from your "regular" builds? Does > std::thread not work with them? If I use std::thread, do I need to > link/distribute any additional libraries? Or are there special licenses > issues? > In short: Why 2 separate builds? > std::thread (an

Re: [Mingw-w64-public] New Rubenvb GCC 4.8 std::thread enabled build

2013-04-02 Thread Baruch Burstein
Can you explain the difference from your "regular" builds? Does std::thread not work with them? If I use std::thread, do I need to link/distribute any additional libraries? Or are there special licenses issues? In short: Why 2 separate builds? On Tue, Mar 26, 2013 at 9:02 PM, Ruben Van Boxem wrot

Re: [Mingw-w64-public] New Rubenvb GCC 4.8 std::thread enabled build

2013-03-26 Thread K. Frank
Hello Ruben! On Tue, Mar 26, 2013 at 3:02 PM, Ruben Van Boxem wrote: > Hi, > > I have uploaded a new GCC 4.8 experimental std::thread build. Nothing > fundamentally changed since the previous posix-threaded builds. Yay! Go Ruben! > Enjoy, Well, I'm not sure that "enjoy" is really the right wo

[Mingw-w64-public] New Rubenvb GCC 4.8 std::thread enabled build

2013-03-26 Thread Ruben Van Boxem
Hi, I have uploaded a new GCC 4.8 experimental std::thread build. Nothing fundamentally changed since the previous posix-threaded builds. Enjoy, Ruben Find the goodies here: http://sourceforge.net/projects/mingw-w64/files/Toolchain%20sources/Personal%20Builds/rubenvb/experimental/ http://source