On 10/21/2013 9:37 PM, Niall Douglas wrote:
On 21 Oct 2013 at 21:23, Edward Diener wrote:
I don't see a gcc 4.6.4 on the MingW sourcforge site ( https://sourceforge.net/projects/mingw/files/MinGW/Base/gcc/Version4/ ). There is a 4.7.0-1 and 4.7.2-1 there, which I have used.
Sure, they're trying to get people off 4.6.x, which is indeed old but trusty. I keep a tarball of it locally.
There is a 4.6.2-1 in the link above, but no 4.6.4. That's why I was wondering why you are specifying 4.6.4.
Is there any Boost library tests of which you know that displays this problem ?
I had no reason to look. I only cared about AFIO, and therefore only cared about its dependencies ASIO and Thread.
Did you find any tests not working in ASIO and Thread when using gcc 4.7+ on up with MingW ? Or was it just in your own work with AFIO ?
I also found a showstopping ICE with my code on a GCC 4.8.x based Mingw which kinda ruled it out for me. I went back to the GCC 4.6.4 based Mingw. It's reliable.
You should really report anything broken in MingW to their bug tracker or mention it in their mailing list. It's possible that the versions on sourceforge have already fixed the problem(s) you have seen. It's also important that users of Boost and MingW understand what may be broken using their particular release.
Mmm. You should look into how Mingw-w64 came about. There is a reason they did a clean room reimplementation.
I will read about it. You are implying that the MingW-w64 people were not happy with the quality of MingW. I will look for information about this.
Also, me personally I have zero time for Mingw given MSVC is free and Mingw binaries are not interoperable with MSVC ones. However Boost peer review wants demonstrated portability, and for that alone I delved into Mingw compatibility. Ordinarily I'd never touch it, except to debug unhelpful MSVC error messages (and even there I prefer clang-win).
It sounds like you able to test clang under Windows using the MingW-w64 RTL and the Boost Build clang toolset.
Does the Boost Build gcc toolset on Windows work correctly with Mingw-w64 ? I have not had any problems with it using MingW itself with Boost Build and don't want to commit to testing against it unless Boost Build works with it.
It worked fine for me. Simply make sure you bootstrap and run b2.exe from inside a Mingw-w64 command box, or else fiddle with PATH to insert Mingw-w64's bin directories for your environment. Otherwise it'll pick up normal Mingw.
Got it. Thanks !