-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/26/2010 11:57 AM, Hartmut Kaiser wrote:
On 4/25/2010 5:08 PM, Hartmut Kaiser wrote:
I'm sorry to say I recompiled everything against Boost trunk (rev. 61561), but the problem still persists. <snip>
Rolling things back now seems like the best strategy. Hartmut, can you rebuild your application against the release branch + the 1.42 version of serialization and let us know if that fixes the problem?
As it turned out the ball is in our court and the problem doesn't seem to be related to serialization (at least it's not a new problem in serialization introduced just recently, but I'll get back to that separately). Please go ahead with the release as planned.
OK, good.
I feel foolish and embarrassed as I have raised a false alarm. I sincerely apologize for the noise and the false conclusions stating the serialization library was broken.
There's no need for that. Raising the (potential) issue before the release went out was the right thing. Better safe than sorry. - -- Eric Niebler BoostPro Computing http://www.boostpro.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJL1gD4AAoJEAeJsEDfjLbXBXEH/3oLIFwfGUarBWKFcztGMMqu oVyflCgEbvBJqu6A8bhcTEUZZ8j5H5pcLNoiJJkzB1DsdxUojr4IMp8nEDH84p/s klMSyZczVAPSMNnvTkiXb8IKk/uhsLkw8KQqYzHwwvV5XwmXJQNCNpuKr2h7xI3p dldryU7QNU8+7T3yLjCT7zUX18cIQNmVgQO6OEFk9VgJmXrbBu5GE6aEVMNMIJxA 0bEgelygteE1rI0WvcdU0RK4Y3QXAJQvsisVdg1SPre2QACZ1AJZty2yngzhxLUo JR7H6KGozUTceLfR+3jcrlolEUsl1wcAb8+R/Cb/qjc0exEaWmN8kcKjenfuGjo= =2uo3 -----END PGP SIGNATURE-----