This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: advise on future of glibc (mktime issue)
- From: Petter Reinholdtsen <pere at hungry dot com>
- To: "Jairo19 at interhosting dot us" <jairo19 at interhosting dot us>
- Cc: libc-alpha at sources dot redhat dot com
- Date: Tue, 7 Jun 2005 16:54:45 +0200
- Subject: Re: advise on future of glibc (mktime issue)
- Bcc: Petter Reinholdtsen <petter dot reinholdtsen at usit dot uio dot no>
- References: <42A5B0C4.7010301@interhosting.us>
[Jairo19@interhosting.us]
> After debugging I see the problem shows up because we call millions
> of times mktime (no way to avoid that for us). The patched glibc (I
> think by RH) has mktime checking for changes on the system's timezone,
Ah, so RedHat actually implemented this fix. Great. I really hope it
make it into the upstream glibc source as well.
If you want some context for this problem, have a look at
<URL:http://sources.redhat.com/bugzilla/show_bug.cgi?id=154>,
<URL:https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133481>, and
<URL:http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=48184>.
So what you consider a bug is considered a feature by others.
Are you sure mktime() is the correct function for you to call?