Bug #10686 Updated: Bug in "mktime()" on values out of bounds

ID: 10686 Updated by: hholzgra@php.net Reported By: dieter@fiebelkorn.net -Status: Open +Status: Analyzed Bug Type: Date/time related Operating System: MacOS X 10.0.2 - 10.1.4 (Darwin) PHP Version: 4.0.5 - 4.2.0 -Assigned To: +Assigned To: hholzgra New Comment: the patch included in this report is almost fine, but it doesn't take in account that the date passed to libc mktime() and the final result with offset applied may be on opposite sides of a DST boundary ... Previous Comments: ------------------------------------------------------------------------ [2002-05-03 03:38:32] sander@php.net Yes you can, using the 'edit submission' button. ------------------------------------------------------------------------ [2002-05-03 02:07:13] dieter@fiebelkorn.net Cannot change to "OPEN"! ------------------------------------------------------------------------ [2002-05-03 02:04:57] dieter@fiebelkorn.net ***************************************************** no FIX was provided for this bug for over a year, so it is being ignoring automatically. ***************************************************** ------------------------------------------------------------------------ [2002-05-03 02:02:39] dieter@fiebelkorn.net I'm unable to compile PHP 4.2 on MacOS X 10.1.4 (Darwin 5.4). But i haven't seen a patch, which solved the described problem! mktime() will used with numbers out of range! Dieter ----- /Users/dieter/Desktop/php-4.2.0/libtool: parse error: condition expected: xno = [3147] /usr/bin/libtool: file: stub.lo is not an object file (not allowed in a library) ------------------------------------------------------------------------ [2002-05-03 00:00:04] php-bugs@lists.php.net No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/10686 -- Edit this bug report at http://bugs.php.net/?id=10686&edit=1