
> > > You don't need to put this check into configure, you can just
> > > do the check after mktime() is used.
> >
> > No, we need that info for the output functions that only use localtime.
> > The intent is, to not use DST before 1970 on platforms that don't have
> > mktime for dates before 1970.
> 
> You can't do execution time checks in configure.  You're going to have to
> do it at run-time.

We do not need any execution time checks for this at all. The objective is
to determine whether mktime works for any results that would be negative.
On AIX and IRIX all calls to mktime for dates before 1970 lead to a result of 
-1, and the configure test is supposed to give a define for exactly that behavior.

Andreas

Fri, 19 Jan 2001 09:15:01 +0100
Zeugswetter Andreas SB  <ZeugswetterA@wien.spardat.at>
AW: AW: AW: AW: AW: AW: Re: tinterval - operator proble
	ms o n AI X
Zeugswetter Andreas SB writes:

> We do not need any execution time checks for this at all. The objective is
> to determine whether mktime works for any results that would be negative.
> On AIX and IRIX all calls to mktime for dates before 1970 lead to a result of
> -1, and the configure test is supposed to give a define for exactly that behavior.

Okay, so you call mktime with a pre-1970 date once when the system starts
up or when the particular function is first used and then save the result
in a static variable.

-- 
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/


Fri, 19 Jan 2001 17:24:27 +0100 (CET)
Peter Eisentraut <peter_e@gmx.net>
Re: AW: AW: AW: AW: AW: AW: Re: tinterval - operator proble
	ms o n AI X