Date: Tue, 21 May 2002 13:14:00 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Alex Vinokur <alexvn AT bigfoot DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: mktime() for 1969 & 2106
In-Reply-To: <acd27n$oa801$1@ID-79865.news.dfncis.de>
Message-ID: <Pine.SUN.3.91.1020521130646.7489B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 21 May 2002, Alex Vinokur wrote:

> It seems that not 'all results for 1969 and 2106' are valid.

That's because your time zone is not GMT0, but something else.  The range 
of times that mktime can represent is defined in the GMT0 zone (a.k.a. 
UTC time); for all other zones, mktime does the appropriate correction.  
That's why the first valid time for your machine is in 1969, not January 
1, 1970.

For the record: what is your timezone, as set on your DJGPP machine?
The headers of your message seem to indicate it's +0400, is that what you 
have on the DJGPP machine?

> Is something wrong?

No.  You just need to make sure your TZ environment variable is set to 
your time zone.  See section 22.20 of the DJGPP FAQ list for more 
details.

Also make sure you have the latest upload of djtzn203.zip from SimTel: 
the initial upload had a bug in the generated timezone files.