
> > > I do not have the original thread where Andreas describes 
> the behavior
> > > of mktime() on his machine. Andreas, can you suggest a 
> simple configure
> > > test to be used?
> >
> > #include <time.h>
> > int main()
> > {
> >     struct tm tt, *tm=&tt;
> >     int i = -50000000;
> >     tm = localtime (&i);
> >     i = mktime (tm);
> >     if (i != -50000000)   /* on AIX this check could also 
> be (i == -1) */
> >     {
> >         printf("ERROR: mktime(3) does not correctly support 
> datetimes before 1970\n");
> >         return(1);
> >     }
> > }
> 
> 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. 

Andreas

Thu, 18 Jan 2001 09:40:44 +0100
Zeugswetter Andreas SB  <ZeugswetterA@wien.spardat.at>
AW: AW: AW: AW: AW: Re: tinterval - operator problems o
	n AI X
Zeugswetter Andreas SB writes:

> > 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.

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


Fri, 19 Jan 2001 00:48:06 +0100 (CET)
Peter Eisentraut <peter_e@gmx.net>
Re: AW: AW: AW: AW: AW: Re: tinterval - operator problems
 o n AI X