| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Mattias Kregert <matti(at)algonet(dot)se>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
| Cc: | "Pedro J(dot) Lobo" <pjlobo(at)euitt(dot)upm(dot)es>, Dwayne Bailey <dwayne(at)mika(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Timezone problems / HAVE_INT_TIMEZINE |
| Date: | 1998-03-19 03:10:20 |
| Message-ID: | 35108C9C.597A252E@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Couldn't this be tested for, just like there is a "flex test" which
> finds out if flex is ok or not? Can the configure script find out and
> add HAVE_INT_TIMEZONE if appropriate?
Uh, it does a test already by trying to compile a program referencing a
global integer variable called "timezone". Somehow a few systems will
compile that but don't really have a useful integer timezone
(RH5.0/glibc2.0 is one of those).
I'm wondering if we could change the sense of the test, to try instead
to test for the presence of a timezone field in the tm structure? That
might fix the glibc2.0 port (assuming it still has problems at v2.0.7;
haven't tested recently) but I don't know which other ports might break.
Can we experiment with this Marc?? Post-megapatch of course :)
- Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas G. Lockhart | 1998-03-19 03:14:41 | Re: [HACKERS] regression testing on linux-elf 2.0.33, postgresql 6.3, i686 |
| Previous Message | Bruce Momjian | 1998-03-19 02:35:56 | Re: [HACKERS] Re: [PATCHES] patches for 6.2.1p6 |