Beman Dawes wrote:
On Fri, Jan 16, 2015 at 4:56 PM, Peter Dimov
wrote: And it has -std=c++11. And clang. What's not to like? Only the fact that gcc.archive fails for some reason, which breaks all tests that want to statically link to Boost.Test.
I'm having failures for gcc on Windows with the three or four Filesystem test that link statically. It looks to me like Boost.Build is missing dependencies, so compiles aren't run soon enough and then the archive fails. So I'm wondering if the same problem is affecting Boost.Test.
Not, it's not that. The problem appears to be that gcc.jam is using g++ -print-prog-name=ar to obtain the path to ar, and this returns /usr/lib/gcc/i686-pc-cygwin/4.8.3/../../../../i686-pc-cygwin/bin/ar.exe which would work in a Cygwin shell, but does not work in a cmd.exe shell, from where I invoke b2. At the moment, I have no idea how this can be fixed.