On Sun, 2002-05-26 at 08:07, Andreas Jaeger wrote:
> Oliver Elphick <olly@lfix.co.uk> writes:
>
> > It seems that Red Hat's latest glibc has introduced a strict
> > interpretation of the ISO C mktime() definition, such that dates before
> > 1970 are now considered to be out of range. This has caused breakage of
> > any application that relies on the old behaviour, such as PostgreSQL.
>
> Please get the facts right: The glibc CVS version has such a change in
The facts are what I wanted to discover.
> it - and Red Hat used as their glibc a version that has this change
> incorporated. The change will be in the next official glibc release
> and has been discussed on the glibc lists,
>
> Andreas
>
> > It is also the case that neither Debian's nor Suse's glibc show this
> > change; nor is it mentioned in their changelogs..
> >
> > Do you know why this change has occurred only in Red Hat's version? Are
> > the distributions' version numbers out of sync?
> >
> > A small program for testing is attached. On Debian's latest libc6 it
> > reports a timestamp of -31712400, but on latest Red Hat it apparently
> > reports -1.
I think you are saying that Red Hat's glibc 2.2.5-3x is not 2.2.5 but a
cvs version beyond 2.2.5. Is that right?
No comment is necessary on the sense or usefulness of the actual
change...
--
Oliver Elphick Oliver.Elphick@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
"Let nothing be done through strife or vainglory; but
in lowliness of mind let each esteem other better than
themselves." Philippians 2:3
Attachment:
signature.asc
Description: This is a digitally signed message part