Subject: Re: [boost] [EXTERNAL] Re: [scope_exit] trunk tests fail on sun compiler
From: Belcourt, K. Noel (kbelco_at_[hidden])
Date: 2012-03-26 13:30:52
On Mar 26, 2012, at 11:13 AM, Vicente J. Botet Escriba wrote:
> Le 26/03/12 17:39, Belcourt, K. Noel a écrit :
>> On Mar 26, 2012, at 6:31 AM, lcaminiti wrote:
>>> Belcourt, K. Noel wrote
>>>> Sun is, for all intent and purposes, a dead platform for us.
>>>> While I
>>>> realize others may be using newer flavors of it, we've basically
>>>> stopped and use it only for the numerics which were/are quite good.
>>>> Our system is not being maintained so I'd guess your best bet is to
>>>> mark your library as unsupported on this platform.
>> Hi Lorenzo,
>>> OK. Shall Sun be removed by the trunk regression tests then?
>> No, we'll leave the Sandia-Sun tester running as long as we can.
>> Go to the Legend at the bottom of the trunk results page, one of
>> the keys is this:
>> n/a The library author marked it as unusable on particular
>> I suggest you mark your library as n/a for the Sandia-Sun tester,
>> as others have done for their libraries, e.g. proto, property_tree,
>> statechart, xpressive, etc...
> it is difficult to classify a library as N/A when we don't know what
> is not working on. I'm wondering if this is not catching a bug on
> the regression tools.
> Boost.Thread is on the same case, and I will be interested in
> changing whatever is needed to make it usable on Sun/Solaris.
> Please, could you see why the regression tests are not showing why
> the test fails?
Oh, I should point out that there's about 500 targets that fail to
link due to missing Boost.Test libraries.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk