Trond Eivind Glomsr�d <[EMAIL PROTECTED]> writes:
> Relying on nonstandardized/nondocumented behaviour is a program bug,
> not a glibc bug.
The question is: how this thing didn't show up before? ISTM that
someone is not doing his work correctly.
> PostgreSQL needs fixing.
Arguably, however, right now is *a lot easier* to fix glibc, and it's
really needed for production systems using postgreSQL and working on
RedHat. But redhat users doesn't matter, the most important thing is
*strict* conformace to standars, right?
> Since we ship both, we're looking at it, but glibc is not the
^^^^^^^^^^^^^^^^^^^
The sad true is: you only answered when the 'Complain to Red Hat'
statement appeared, not a single word before and not a single word
when the bug report were closed. I'm really disappointed.
The nice thing is: glibc is free software and we don't have to wait or
relay on some of the redhat staff members (thanks god) for this to get
fixed or say: for the standard to get extended again. The patch to
glibc is pretty straightforward and attached.
Regards,
Manuel.
--- glibc-2.2.5/time/mktime.c.org Tue May 21 11:37:06 2002
+++ glibc-2.2.5/time/mktime.c Tue May 21 11:39:28 2002
@@ -259,11 +259,13 @@
int sec_requested = sec;
+#if 0
/* Only years after 1970 are defined.
If year is 69, it might still be representable due to
timezone differnces. */
if (year < 69)
return -1;
+#endif
#if LEAP_SECONDS_POSSIBLE
/* Handle out-of-range seconds specially,
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
