| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Peter Eisentraut'" <peter_e(at)gmx(dot)net> |
| Cc: | "'thomas(at)pgsql(dot)com'" <thomas(at)pgsql(dot)com>, lockhart(at)fourpalms(dot)org, Pete Forman <pete(dot)forman(at)westerngeco(dot)com>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | AW: AW: AW: AW: AW: AW: Re: tinterval - operator proble ms o n AI X |
| Date: | 2001-01-19 08:15:01 |
| Message-ID: | 11C1E6749A55D411A9670001FA6879633681C5@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2001-01-19 09:28:09 | Re: Changes to include files |
| Previous Message | Tom Lane | 2001-01-19 07:04:04 | Re: 7.1beta3-2 RPMset uploading. |