Re: [Mingw-w64-public] GCC 4.7 prerelease rubenvb Personal build 4.7.0-1

[Joshua B. <rap...@ra...>]

Well, looks like I was able to get it working before I have to go out. Took
much less time than expected.

Not sure how much of a hack this is, but I have fixed the problem by adding
the following to my b2 command line:
define=BOOST_USE_WINDOWS_H define=_GLIBCXX_HAVE_GTHR_DEFAULT

The former fixes problems with the interlocked APIs not being found, and
the latter fixes BOOST_DISABLE_THREADS being incorrectly defined.

A quick skim through the Boost bug tracker indicates that the threading
problems with GCC 4.7 is a known issue, however it is yet to be resolved.
Perhaps someone more knowledgeable in the workings of libstdc++ could
provide a patch compatible with MinGW-w64?

Thanks again Ruben.

On Sun, Jan 15, 2012 at 8:33 AM, Joshua Boyce <rap...@ra...
> wrote:

> Hey, have you tested this toolchain with Boost? I can't get Thread to
> build anymore (which in turn means Locale no longer builds) and I wanted to
> make sure it wasn't just me. I'm hoping it's just a simple configuration
> problem, but I don't have time to investigate until later tonight.
>
> Thanks for keeping these toolchains updated btw. Much appreciated.
>
> On Sun, Jan 15, 2012 at 12:06 AM, Ruben Van Boxem <
> van...@gm...> wrote:
>
>> Hi everyone,
>>
>> Today I uploaded a new set of toolchains built with:
>>  - binutils trunk
>>  - GCC 4.7 (trunk)
>>  - MinGW-w64 v2.x stable branch
>>  - gdb trunk
>>  - Clang/LLVM trunk
>> in short, all the latest greatness
>>
>> This GCC is built with internal posix threading (like the last four
>> versions I built), as to enable the <thread> and <chrono> features in
>> libstdc++. One caveat that is still present: if you use std::thread, you'll
>> need to link with "-static", otherwise the thread's join() function will
>> throw an exception.
>>
>> What changed?
>>  - no Mac build: the GCC 4.7 build system doesn't seem to work for me in
>> this case
>>  - I added "-static" to my link commands, so that all the GCC executables
>> should be independent of the GCC runtime dll's, allowing you to call the
>> programs without first adding the "bin" directory to PATH. This changes
>> nothing for programs built with this toolchain.
>>
>> If you find any issues, please report them and I'll see what I can do to
>> help. Please try out Clang and pester their bugtracker/mailing list with
>> Windows issues you discover ;-) I do believe there are some compatibility
>> issues with libstdc++ popping up. Usability might be reduced since the GCC
>> 4.6 builds.
>>
>> Ruben
>>
>> PS: download links:
>>
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/4.7.0-1/
>>
>> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/4.7.0-1/
>>
>> http://sourceforge.net/projects/mingw-w64/files/Toolchain%20sources/Personal%20Builds/rubenvb/gcc-4.7.0-1_rubenvb.tar.lzma
>>
>>
>> ------------------------------------------------------------------------------
>> RSA(R) Conference 2012
>> Mar 27 - Feb 2
>> Save $400 by Jan. 27
>> Register now!
>> http://p.sf.net/sfu/rsa-sfdev2dev2
>> _______________________________________________
>> Mingw-w64-public mailing list
>> Min...@li...
>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>>
>>
>