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: Beman Dawes (bdawes_at_[hidden])
Date: 2011-09-14 14:59:23

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.

--Beman