On Fri, 6 Oct 2000, Dave Huang wrote:

: Yeah, that does seem to be the problem... when loading in the timezone
: info, it's stuffing the GMT offset into a 64-bit long rather than 32-bit
: int, so negative offsets are being treated as huge positive offsets. The
: patch below seems to fix the problem for me.

Try just "int"; "int32_t" diesn't exist on all platforms, and "int" may well
be accepted back into the MySQL source base.

-- 
-- Todd Vierling <tv@wasabisystems.com>  *  http://www.wasabisystems.com/
-- Speed, stability, security, and support.  Wasabi NetBSD:  Run with it.