[Bug 1021161] New: Perl mktime() still not Y2K38 compatible (even it should be)?

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1021161

            Bug ID: 1021161
           Summary: Perl mktime() still not Y2K38 compatible (even it
                    should be)?
           Product: Fedora
           Version: 18
         Component: perl
          Severity: medium
          Assignee: jplesnik at redhat.com
          Reporter: redhat-bugzilla at linuxnetz.de
        QA Contact: extras-qa at fedoraproject.org
                CC: cweyl at alumni.drew.edu, iarnell at gmail.com,
                    jplesnik at redhat.com, kasal at ucw.cz,
                    perl-devel at lists.fedoraproject.org, ppisar at redhat.com,
                    psabata at redhat.com, rc040203 at freenet.de,
                    tcallawa at redhat.com



Description of problem:
According to http://search.cpan.org/~jesse/perl-5.12.0/pod/perl5120delta.pod,
Perl 5.12 (and later) should be Y2K38 compatible. However POSIX::mktime() for 
2040 is still returning undef. I am wondering about "Sizeof time_t = 4" in the
build log for i686 as well, shouldn't that be 8 when using -Duse64bitint and/
or -Duselongdouble? Or am I on the wrong path?

Version-Release number of selected component (if applicable):
perl-5.16.3-244.fc18

How reproducible:
Run the following on a 32 bit system:
perl -e 'use POSIX; print mktime(0, 0, 0, 1, 0, 140, 0, 0) . "\n"'

Actual results:
Perl mktime() still not Y2K38 compatible (even it should be)?

Expected results:
2208985200 :)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6jneoVeN3K&a=cc_unsubscribe