Re: [Boost-testing] process_jam_log.exe fails under mingw-w64 gcc-4.7

Subject: Re: [Boost-testing] process_jam_log.exe fails under mingw-w64 gcc-4.7
From: Jim Bell (Jim_at_[hidden])
Date: 2011-09-15 12:21:55

On 1:59 PM, Beman Dawes wrote:
> On Wed, Sep 14, 2011 at 11:19 AM, Jim Bell<Jim_at_[hidden]>  wrote:
>> My new boost regression test for mingw-w64, gcc-4.7, fails at
>> process_jam_log...
>>
>>
>> "F:\boost\GCC\release\tools_regression\build\bin\gcc-mingw-4.7.0\release\process_jam_log.exe"
>>    "F:\boost\GCC\release\results" 0<"F:\boost\GCC\release\results\bjam.log"
>>
>>    terminate called after throwing an instance of
>>    'boost::filesystem3::filesystem_error'
>>       what():  boost::filesystem::status: The operation completed
>>    successfully: "F:\boost\GCC\release\boost\status\libs"
>>
>>    This application has requested the Runtime to terminate it in an
>>    unusual way.
>>    Please contact the application's support team for more information.
>>
>> Any ideas on the failure or a good work-around?  --pjl-toolkit?
> Where did you get the binary for gcc 4.7.0?
>
> Have you tried building with gcc 4.5.x or earlier? I've had a lot of
> trouble with 4.6.0 and later WRT exceptions that should have been
> caught not getting caught.

Putting a pre-built process_jam_log.exe in the regression root dir is 
the way I'm going. (Same for bjam.exe, btw. The python script picks them 
both up.) So I'm using one built for VC8. No reason to get 
"experimental" with these pieces-parts.

I'm using 
<http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/4.7.0-stdthread/>.