From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
Cc: | phd(at)sun(dot)med(dot)ru, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Date/time on glibc2 linux |
Date: | 1998-12-10 15:48:41 |
Message-ID: | 12577.913304921@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Thomas G. Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> If the tm structure contains the timezone info (as it claims to on my
> RH5.1 glibc2 system) then for testing try to #undef HAVE_INT_TIMEZONE in
> config.h and see how it goes. If I have a chance tomorrow I'll try doing
> the same at work. I'm guessing that our configure tests look for the
> global variable version first, and that the glibc2 passes that test even
> though the other mechanism is the right one.
Yes, the autoconf test just checks for a global variable "timezone"
declared in <time.h>. It'd probably be better to reverse the test to
check for the timezone fields in a struct tm. I don't much care for
the name of the configuration symbol either ... maybe change it to
HAVE_STRUCT_TM_TZ_FIELDS ?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Broytmann | 1998-12-10 16:34:12 | Re: [HACKERS] Date/time on glibc2 linux |
Previous Message | Sferacarta Software | 1998-12-10 13:41:17 | Re[2]: AW: [HACKERS] isnull() or is it?t |