ID:               20268
 Updated by:       [EMAIL PROTECTED]
 Reported By:      bdabney at dallasnews dot com
-Status:           Critical
+Status:           Closed
 Bug Type:         Scripting Engine problem
 Operating System: any 64bit
 PHP Version:      4CVS-2002-11-05
 New Comment:

[To: j-devenish at users dot sourceforge dot net]

Most of the critical issues are now fixed in CVS.
If there are any left, please open new bug report for them.




Previous Comments:
------------------------------------------------------------------------

[2003-03-14 03:13:51] j-devenish at users dot sourceforge dot net

Although the original title of this bug was something to do with the
CLI crashing during the installation process, the title is now 64-bit
PHP 4.3.

Regarding the status of 4.3.2RC1, some known problems (not new ones)
are:

 - ./configure wants to compare hard-coded paths when finding some
   module libraries, rather than testing the compiler and linker
   themselves. This affects RedHat and SUSE Linux as well as
   Solaris, at least.
 - test cases have flaws that cause them to fail on LP64 systems
   although the failures aren't necessarily caused by any 64-bit
   problems in the code. This affects Solaris, at least.
 - various int/void* confusion (crash-causing). This affects
   Solaris, at least.

These have been reported in the bug system and discussed on php-dev
(and php-internals and php-qa). Although it was along time coming,
some partial fixes were applied between 4.3.0 and 4.3.1RC1.

------------------------------------------------------------------------

[2003-03-12 02:08:11] j-devenish at users dot sourceforge dot net

FWIW, I installed a "Stable (4.3.x-dev)" snapshot! After ./configure
modifications (relating to hard-coded library paths -- that affects
64-bit RedHat, too, so maybe it will get fixed) it compiled and
installed without crashing. Importantly, this out-of-the-box PHP
actually serves files without crashing (though I get compile warnings
regarding ostensibly non 64 bit-clean code).

One odd thing though: Apache reports that it is running 4.3.0-pre2. In
contrast, Apache reports 4.3.2-dev when I have my php4 (PHP_4_3)
checkout installed.

After modifying the Makefile to run the 'test' target, that does
something, too. It results in a few core dumps, and a few tests still
assume that values are limited to 32-bit precision, but 4.3.2 is still
a step up for anyone who hasn't been able to use PHP 4.3 yet.

------------------------------------------------------------------------

[2003-03-10 08:56:43] [EMAIL PROTECTED]

Most, if not all issues should now be fixed.
Please give the latest stable snapshot a go.
(http://snaps.php.net/)


------------------------------------------------------------------------

[2003-03-04 19:51:26] [EMAIL PROTECTED]

Need to be addressed before 4.3.2 goes out the door.


------------------------------------------------------------------------

[2003-02-23 04:36:04] [EMAIL PROTECTED]

http://news.php.net/article.php?group=php.bugs&article=24417
http://news.php.net/article.php?group=php.bugs&article=24418



------------------------------------------------------------------------

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/20268

-- 
Edit this bug report at http://bugs.php.net/?id=20268&edit=1

Reply via email to