Re: [boost] [1.33.0] Release status and updated timeline

From: Douglas Gregor (doug.gregor_at_[hidden])
Date: 2005-07-08 07:42:18

On Jul 8, 2005, at 12:14 AM, Robert Ramey wrote:

> Douglas Gregor wrote:
>> 1. The Serialization lib is failing many of its regression tests. We
>> need to get these under control.
>
> Summary of pending issues related to the seriaization library.
>
> Issues I can deal with
>
> a) msvc - serialization of exported pointers broke due to a recent 
> change
> made to better handle some aspects of abstract base classes.

Okay.

> b) TRU64 and CW - experiments are on-going in getting compilers
> instanticiate code not explicitly referenced.  Due to the efforts of 
> Rene
> Rivera, much progress has been made on CW but there is still a way to 
> go.

CodeWarrior is higher priority than Tru64 for this release.

> Issues that I can't deal with
>
> a) cw- 9_5- darwin - this fails in execution of all DLL versions of the
> library.
> b) acc - looks pretty good - but all DLL versions fail

I'll mark these up as an unresearched problem with shared libraries for 
that compiler.

> c) gcc- 2.95.3- stlport- 4.6.2- linux doesn't seem to have SPIRIT_ROOT 
> set
> and pointing to a copy of spirit 1.6x.  The serialization library and 
> tests
> are therefore skipped resulting in white space in the table

Okay, that's fine.

> d) gcc (Beman) I presume this is cygwin which doesn't support wide 
> character
> i/o.  If this toolset name were changed to gcc-cygwin, these tests 
> would be
> skipped and results would show as white space.

It's not a release platform, so don't worry about it. Only those 
compilers that show up in the "release view" are important for the 
release.

> e) como- 4_3_3- vc7_1 - There is some sort of conflict between the
> serialization library and the test library. The results in both
> instantiating code for streams which results in a linkage error.  I 
> made an
> inquiry to Commeau and here is the response I get:
>
> [snip comeau response]
> I'm still digesting this.

Again, not a release platform, so don't worry about it.

> f) RudbekAssociates results show a recent date/time but contain error
> message which refer to functions that are no longer in the library.  I
> believe that something needs to be refreshed here.

This is a known issue with incremental testing; send a note to the 
boost-regression mailing lists asking for  RudbekAssociates to clear 
out the old results for the Serialization lib.

> g) last time I checked SunOS, DMC and vacpp failed to build the 
> library due
> to failures in code outside the serialization library.  Generally I 
> have
> marked these compilers as not usable.

Don't worry about these, either.

        Doug