"Richard Jennings"
My application that works with 1.32 is failing to link with 1.33 RC1 due to boost::serialization::void_cast_register (specialised for my classes) being an unresolved external.
In my case these errors were all a result of the new rule that 'serialization' header includes may only appear _after_ 'archive' headers.(which looks to be the case in the code provided) Moving the serialization includes into the translation unit where the archive/serialization code is actually instantiated cleared these errors. This did bring up an issue of needing to forward declare boost::serialization::access. If this header ordering limitation/requirement is here to stay, some sort of forwarding header should probably be provided. Jeff Flinn