From: | Oleg Broytmann <phd(at)sun(dot)med(dot)ru> |
---|---|
To: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Date/time on glibc2 linux |
Date: | 1998-12-09 15:16:01 |
Message-ID: | Pine.SOL2.3.96.SK.981209180752.8389A-100000@sun.med.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello!
I think, finally, that the simplest way to solve this would be patch
configure, not datetime.c, dt.c and all that.
The struct tm on linux has tm_gmtoff and tm_zone, so it will be enough
if postgres' configure undefine HAVE_TZSET and HAVE_INT_TIMEZONE on glibc2.
Python's configure.in has the following:
# checks for structures
AC_HEADER_TIME
AC_STRUCT_TM
AC_STRUCT_TIMEZONE
and this do all neccessary defines. I think postgres' configure will
require some more tricks.
Continue investigating...
Oleg.
----
Oleg Broytmann http://members.tripod.com/~phd2/ phd2(at)earthling(dot)net
Programmers don't die, they just GOSUB without RETURN.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas G. Lockhart | 1998-12-09 15:21:53 | Re: AW: [HACKERS] isnull() or is it?t |
Previous Message | Bruce Momjian | 1998-12-09 15:10:07 | Re: AW: [HACKERS] isnull() or is it?t |