Anthony Williams wrote:
"John Maddock" <john@johnmaddock.co.uk> writes:
Ok, I've looked at it. It clearly looks like a DST related problem. I can't tell if it's a machine configuration problem or a library problem...I just know it's something boost date-time can't really fix. Essentially the problem is that std::local_time and std::gmtime are returning a time that's 1 hour ahead GetSystemTimeAsFileTime. So unless the owner of the machine can diagnose why this has started I guess we should mark this one as expected. I can reproduce this here: the test fails with Borland 5.8.2 and 5.6.4 but
Jeff Garland wrote: passes with msvc-8, intel-9.1 and mingw32. So it's a runtime library issue, not a system one by the looks of it.
That's a known bug in the Borland library. Well, known to some people, anyway: I was told about that bug a few months ago in an unrelated discussion. I don't remember whether there was a workaround.
I've marked this as expected now :-( Jeff