> 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 :)
In response to
pgsql-hackers by date
|Next:||From: Thomas G. Lockhart||Date: 1998-03-19 03:14:41|
|Subject: Re: [HACKERS] regression testing on linux-elf 2.0.33, postgresql 6.3, i686|
|Previous:||From: Bruce Momjian||Date: 1998-03-19 02:35:56|
|Subject: Re: [HACKERS] Re: [PATCHES] patches for 6.2.1p6|