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

ID: 10686 Updated by: hholzgra@php.net Reported By: dieter@fiebelkorn.net -Status: Analyzed +Status: Closed 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: hholzgra New Comment: fixed in latest CVS, should work on all OS/libc versions now as negative offsets are now taken care of internaly so libc mktime() won't receive any negative (or 0 for tm_mday) values anymore (see also #8828) Previous Comments: ------------------------------------------------------------------------ [2002-06-12 09:05:30] hholzgra@php.net 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 ... ------------------------------------------------------------------------ [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) ------------------------------------------------------------------------ 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