If you suspect the compiler I would run the whole test suite. It might take overnight - but its much better then waiting for anomolies to appear in your code and trying to track them down on a case by case basis. You can run just the serialization part of the test suite, but you might as well just follow the instructions with 1.33 and just re-run the whole thing. That wil give you table of any and all issues the version of the compiler you're using might have. Robert Ramey vermaaso wrote:
On Wed, Dec 13, 2006 at 08:29:40AM -0800, Robert Ramey wrote:
I would be very interested in getting to the bottom of the problem. This would likely result in a small tweak which would make the library more portable. Of course I realise that this is not that easy. Note that I test here with gcc 3.3 under cywin. So I would be hopeful that its easily fixable. I don't know what version of boost your using, but it may already be fixed in a later version.
According to the website of Novell, they use 'GCC 3.3.3 enhanced by the SUSE labs team'. I need to a run patch on this system, but I'm not sure whether this patch will affect gcc. I'll try it anyway and run the same tests again. I'll report the results back later (probably tomorow).
If you have any suggestions or tests you want me to run on this system just let me know.
The boost version is boost 1_33_1. I'll check for a newer version also.
Regards, Oscar