Le 27/03/12 20:17, Belcourt, K. Noel a écrit :
On Mar 27, 2012, at 10:59 AM, Vicente J. Botet Escriba wrote:
Le 26/03/12 19:30, Belcourt, K. Noel a écrit :
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 platform/toolset.
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...
Noel,
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.
Thanks for the information. The last test I have been adding to Boost.Thread doesn't use Boost.Test, but the link to Boost.Test is done however. I will dissociate it to see if this helps.
I'm most interested in hearing if Thread (sans Test) will work on Sun.
Me too. Note that some test are using yet Boost.Test. Committed revision 77588. Best, Vicente