Everything
php
Learn Community Releases The PHP Project
Home » Project » Newsgroups » php.internals » 5.2.4RC3 »

5.2.4RC3

php.internals

Ilia A.

19 years ago
Only a week has passed and we are up to RC3 already, only 5 new fixes since last RC one which addresses a minor security issue, which I wanted to resolve before the final release. The source tarball can be found at the URL below and Win32 binaries will be available shortly. http://downloads.php.net/ilia/php-5.2.4RC2.tar.bz2 (md5sum: dc6589d253b4ac5010603c5927f33546 ) Please try this RC out on your code and report back any critical issues you may discover. If all goes well the plan is to have the final release done by the end of next week. Ilia Alshanetsky 5.2 Release Master

Ilia A.

19 years ago
The link in the previous e-mail was wrong, the correct location of the tarball is: http://downloads.php.net/ilia/php-5.2.4RC3.tar.bz2 (md5sum: 72371ec077dd393f0c7d6370d115dcb6) On 23-Aug-07, at 8:22 PM, Ilia Alshanetsky wrote:
> Only a week has passed and we are up to RC3 already, only 5 new > fixes since last RC one which addresses a minor security issue, > which I wanted to resolve before the final release. The source > tarball can be found at the URL below and Win32 binaries will be > available shortly. > > http://downloads.php.net/ilia/php-5.2.4RC2.tar.bz2 (md5sum: > dc6589d253b4ac5010603c5927f33546 ) > > Please try this RC out on your code and report back any critical > issues you may discover. If all goes well the plan is to have the > final release done by the end of next week. > > Ilia Alshanetsky > 5.2 Release Master >
Ilia Alshanetsky

Dale Walsj

19 years ago
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Aug 23, 2007, at 21:19:52, Ilia Alshanetsky wrote:
> The link in the previous e-mail was wrong, the correct location of > the tarball is: > > http://downloads.php.net/ilia/php-5.2.4RC3.tar.bz2 (md5sum: > 72371ec077dd393f0c7d6370d115dcb6) > > > On 23-Aug-07, at 8:22 PM, Ilia Alshanetsky wrote: > >> Only a week has passed and we are up to RC3 already, only 5 new >> fixes since last RC one which addresses a minor security issue, >> which I wanted to resolve before the final release. The source >> tarball can be found at the URL below and Win32 binaries will be >> available shortly. >> >> http://downloads.php.net/ilia/php-5.2.4RC2.tar.bz2 (md5sum: >> dc6589d253b4ac5010603c5927f33546 ) >> >> Please try this RC out on your code and report back any critical >> issues you may discover. If all goes well the plan is to have the >> final release done by the end of next week. >> >> Ilia Alshanetsky >> 5.2 Release Master >> > > Ilia Alshanetsky
It fails to generate a working binary for Mac OSX 10.4.10 on an intel XServe that doesn't segfault, I'm sure it's nothing critical since I've experienced similar issues with other RC versions that seem to be resolved with official releases. It's not worth me spending time on since I have other PHP build issues that are far more important like why 5.2.3 wont generate a thread safe binary for apache 1.3.33 or the binaries are thread safe and the modules aren't or the reverse (I haven't figured out which is the case yet and no one seems to be of any help so far).
> > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php
- -- BuildSmart -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFGzjkj0hzWbkf0eKgRAvijAJ9ob6UW2SirCrjJoasBQ4ocaQfs0gCfe6Vk 4oZgDdLQti6Bc0I8XBHvlwk= =ORte -----END PGP SIGNATURE-----

Ilia A.

19 years ago
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23-Aug-07, at 9:49 PM, BuildSmart wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Aug 23, 2007, at 21:19:52, Ilia Alshanetsky wrote: > >> The link in the previous e-mail was wrong, the correct location of >> the tarball is: >> >> http://downloads.php.net/ilia/php-5.2.4RC3.tar.bz2 (md5sum: >> 72371ec077dd393f0c7d6370d115dcb6) >> >> >> On 23-Aug-07, at 8:22 PM, Ilia Alshanetsky wrote: >> >>> Only a week has passed and we are up to RC3 already, only 5 new >>> fixes since last RC one which addresses a minor security issue, >>> which I wanted to resolve before the final release. The source >>> tarball can be found at the URL below and Win32 binaries will be >>> available shortly. >>> >>> http://downloads.php.net/ilia/php-5.2.4RC2.tar.bz2 (md5sum: >>> dc6589d253b4ac5010603c5927f33546 ) >>> >>> Please try this RC out on your code and report back any critical >>> issues you may discover. If all goes well the plan is to have the >>> final release done by the end of next week. >>> >>> Ilia Alshanetsky >>> 5.2 Release Master >>> >> >> Ilia Alshanetsky > > It fails to generate a working binary for Mac OSX 10.4.10 on an > intel XServe that doesn't segfault, I'm sure it's nothing critical > since I've experienced similar issues with other RC versions that > seem to be resolved with official releases.
That's strange, I've compiled RC2 on my Intel mac and it seems to be working fine without any issues. Could this perhaps be related to some of the modules you have enabled?
> > It's not worth me spending time on since I have other PHP build > issues that are far more important like why 5.2.3 wont generate a > thread safe binary for apache 1.3.33 or the binaries are thread > safe and the modules aren't or the reverse (I haven't figured out > which is the case yet and no one seems to be of any help so far).
Apache 1 sapi does not need to thread-safe since Apache 1 does not use threads. Ilia Alshanetsky -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFGzjoNLKekh381/CERAprBAKCYf7Z/ptM6ZQ9SiIxSWtP/Ew/6+QCfUfQk dmRMo9bGTSdGSXp3lKwVRAA= =BaIb -----END PGP SIGNATURE-----

Dale Walsj

19 years ago
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Aug 23, 2007, at 21:53:17, Ilia Alshanetsky wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On 23-Aug-07, at 9:49 PM, BuildSmart wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> On Aug 23, 2007, at 21:19:52, Ilia Alshanetsky wrote: >> >>> The link in the previous e-mail was wrong, the correct location >>> of the tarball is: >>> >>> http://downloads.php.net/ilia/php-5.2.4RC3.tar.bz2 (md5sum: >>> 72371ec077dd393f0c7d6370d115dcb6) >>> >>> >>> On 23-Aug-07, at 8:22 PM, Ilia Alshanetsky wrote: >>> >>>> Only a week has passed and we are up to RC3 already, only 5 new >>>> fixes since last RC one which addresses a minor security issue, >>>> which I wanted to resolve before the final release. The source >>>> tarball can be found at the URL below and Win32 binaries will be >>>> available shortly. >>>> >>>> http://downloads.php.net/ilia/php-5.2.4RC2.tar.bz2 (md5sum: >>>> dc6589d253b4ac5010603c5927f33546 ) >>>> >>>> Please try this RC out on your code and report back any critical >>>> issues you may discover. If all goes well the plan is to have >>>> the final release done by the end of next week. >>>> >>>> Ilia Alshanetsky >>>> 5.2 Release Master >>>> >>> >>> Ilia Alshanetsky >> >> It fails to generate a working binary for Mac OSX 10.4.10 on an >> intel XServe that doesn't segfault, I'm sure it's nothing critical >> since I've experienced similar issues with other RC versions that >> seem to be resolved with official releases. > > That's strange, I've compiled RC2 on my Intel mac and it seems to > be working fine without any issues. Could this perhaps be related > to some of the modules you have enabled?
I was just getting around to that now, seems that if I enable dio, xmlrpx, xsl and zip is where it breaks down, if I build them embedded it seems to work OK. Of course I can't get the fbsql module to work at all under apache 2 regardless of how I build it.
> >> >> It's not worth me spending time on since I have other PHP build >> issues that are far more important like why 5.2.3 wont generate a >> thread safe binary for apache 1.3.33 or the binaries are thread >> safe and the modules aren't or the reverse (I haven't figured out >> which is the case yet and no one seems to be of any help so far). > > Apache 1 sapi does not need to thread-safe since Apache 1 does not > use threads.
True but by enabling it (or I thought) I could generate a single set of modules that could be used with apache 1 and apache 2 but it doesn't seem to matter to the apache 1 sapi, if I build the modules under apache 1 and force flat_namespace most of the modules seem to work under apache2 but I can't get any of the apache 2 build modules to work properly even in apache 2, I get that missing symbol issue however I don't get the issue if I build them embeded.
> Ilia Alshanetsky
- - -- BuildSmart -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFGzj9C0hzWbkf0eKgRAn1wAJ4oAVcgOreaI0Udixx7JPn6fKn+yACeK+rd b/jSaG5Tt/kkzHHNCh+jiIo= =P2u6 -----END PGP SIGNATURE-----

Rasmus Lerdorf

19 years ago
BuildSmart wrote:
> True but by enabling it (or I thought) I could generate a single set of > modules that could be used with apache 1 and apache 2 but it doesn't > seem to matter to the apache 1 sapi, if I build the modules under apache > 1 and force flat_namespace most of the modules seem to work under > apache2 but I can't get any of the apache 2 build modules to work > properly even in apache 2, I get that missing symbol issue however I > don't get the issue if I build them embeded.
Note that you take a significant performance hit by building it threaded. -Rasmus

Dale Walsj

19 years ago
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Aug 23, 2007, at 22:31:37, Rasmus Lerdorf wrote:
> BuildSmart wrote: >> True but by enabling it (or I thought) I could generate a single >> set of >> modules that could be used with apache 1 and apache 2 but it doesn't >> seem to matter to the apache 1 sapi, if I build the modules under >> apache >> 1 and force flat_namespace most of the modules seem to work under >> apache2 but I can't get any of the apache 2 build modules to work >> properly even in apache 2, I get that missing symbol issue however I >> don't get the issue if I build them embeded. > > Note that you take a significant performance hit by building it > threaded.
Yes but you can't build for apache2 without building threaded and I believe because I force enable it in 1.3.33 doesn't mean it's used, and as far as I can tell it's only referencing a couple of symbols that aren't threading so it shouldn't be an issue. I'm just trying to find a happy medium where I can have a single install with 40 loadable extensions that can be used by 3 different versions of apache. It would be nice if there was some kind of flag form the sapi module that could be used to switch the module directory, then it wouldn't be an issue to have an install but two sets of modules, one that is used for the thread required and the other by non-threaded. So far it seems to always ut the modules in "no-debug-non- zts-20060613" and one would conclude that for the apache 2's which are thread safe would be in "no-debug-20060613" but this isn't where they are installing to. SEE: http://amavis-stats.com/php-5.2.3.tgz (a little over 100MB compressed - dependancies included), the only module that doesn't work is rar. I've included my own modules and the RRDTool framework so you can have a look at what's going on. The rar problem isn't a really big issue, I can program a work-around since it's only one customer who requires it and when time permits I can look at it and see what the problem is and why it doesn't work as a loadable module under apache 2 (at all).
> > -Rasmus
- -- Dale -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFGzlpR0hzWbkf0eKgRAoBeAKC8PIDD49DCVgk6asvBen+Sg+c5AgCfePpc i4rME8Cb+EOik3giH4WJ5H8= =o+PN -----END PGP SIGNATURE-----

Rasmus Lerdorf

19 years ago
BuildSmart wrote:
> > On Aug 23, 2007, at 22:31:37, Rasmus Lerdorf wrote: > >> BuildSmart wrote: >>> True but by enabling it (or I thought) I could generate a single set of >>> modules that could be used with apache 1 and apache 2 but it doesn't >>> seem to matter to the apache 1 sapi, if I build the modules under apache >>> 1 and force flat_namespace most of the modules seem to work under >>> apache2 but I can't get any of the apache 2 build modules to work >>> properly even in apache 2, I get that missing symbol issue however I >>> don't get the issue if I build them embeded. > >> Note that you take a significant performance hit by building it threaded. > > Yes but you can't build for apache2 without building threaded
That seems like a strange limitation. Whether Apache2 needs a threaded module depends entirely on the MPM you use. The default MPM in most distros is prefork which is a non-threaded MPM and as such you are much better off building PHP non-threaded if that is the MPM you are going to be using. -Rasmus

Dale Walsj

19 years ago
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Aug 24, 2007, at 01:08:50, Rasmus Lerdorf wrote:
> BuildSmart wrote: >> >> On Aug 23, 2007, at 22:31:37, Rasmus Lerdorf wrote: >> >>> BuildSmart wrote: >>>> True but by enabling it (or I thought) I could generate a single >>>> set of >>>> modules that could be used with apache 1 and apache 2 but it >>>> doesn't >>>> seem to matter to the apache 1 sapi, if I build the modules >>>> under apache >>>> 1 and force flat_namespace most of the modules seem to work under >>>> apache2 but I can't get any of the apache 2 build modules to work >>>> properly even in apache 2, I get that missing symbol issue >>>> however I >>>> don't get the issue if I build them embeded. >> >>> Note that you take a significant performance hit by building it >>> threaded. >> >> Yes but you can't build for apache2 without building threaded > > That seems like a strange limitation. Whether Apache2 needs a > threaded > module depends entirely on the MPM you use. The default MPM in most > distros is prefork which is a non-threaded MPM and as such you are > much > better off building PHP non-threaded if that is the MPM you are > going to > be using.
HMM... that's something I didn't think of, let me try that out for size and I'll report my results.
> > -Rasmus
- -- BuildSmart -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFGznkO0hzWbkf0eKgRAmOfAKCFLl8rXwkGw0rzz9dyo8r3WEohwgCdHuFj Y8JkriAlIZVL8aUVzqXQbFM= =6HF5 -----END PGP SIGNATURE-----

Stanislav Malyshev

19 years ago
> Yes but you can't build for apache2 without building threaded and I
Of course you can. That depends on MPM apache is using.
-- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com

Dale Walsj

19 years ago
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Aug 24, 2007, at 02:35:40, Stanislav Malyshev wrote:
>> Yes but you can't build for apache2 without building threaded and I > > Of course you can. That depends on MPM apache is using.
Unfortunately Apple builds the supplied apache 2.0.53 as worker so my decision is to provide 2.2.4 as prefork and not support the 2.0.53, this means I should be able to go back to the flat_namespace convention and everything should work (in theory, building it all and testing it first) as a single installation (except for the sapi's.
> -- > Stanislav Malyshev, Zend Software Architect > stas@zend.com http://www.zend.com/ > (408)253-8829 MSN: stas@zend.com
- -- BuildSmart -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFGzor10hzWbkf0eKgRAmbHAKCIsMaBV/8GglMHlAWEr38y5/riGwCeOz9T RN7yuf4nNN9sHFbvbBk1k+o= =g31X -----END PGP SIGNATURE-----

Dale Walsj

19 years ago
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Aug 23, 2007, at 21:53:17, Ilia Alshanetsky wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On 23-Aug-07, at 9:49 PM, BuildSmart wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> On Aug 23, 2007, at 21:19:52, Ilia Alshanetsky wrote: >> >>> The link in the previous e-mail was wrong, the correct location >>> of the tarball is: >>> >>> http://downloads.php.net/ilia/php-5.2.4RC3.tar.bz2 (md5sum: >>> 72371ec077dd393f0c7d6370d115dcb6) >>> >>> >>> On 23-Aug-07, at 8:22 PM, Ilia Alshanetsky wrote: >>> >>>> Only a week has passed and we are up to RC3 already, only 5 new >>>> fixes since last RC one which addresses a minor security issue, >>>> which I wanted to resolve before the final release. The source >>>> tarball can be found at the URL below and Win32 binaries will be >>>> available shortly. >>>> >>>> http://downloads.php.net/ilia/php-5.2.4RC2.tar.bz2 (md5sum: >>>> dc6589d253b4ac5010603c5927f33546 ) >>>> >>>> Please try this RC out on your code and report back any critical >>>> issues you may discover. If all goes well the plan is to have >>>> the final release done by the end of next week. >>>> >>>> Ilia Alshanetsky >>>> 5.2 Release Master >>>> >>> >>> Ilia Alshanetsky >> >> It fails to generate a working binary for Mac OSX 10.4.10 on an >> intel XServe that doesn't segfault, I'm sure it's nothing critical >> since I've experienced similar issues with other RC versions that >> seem to be resolved with official releases. > > That's strange, I've compiled RC2 on my Intel mac and it seems to > be working fine without any issues. Could this perhaps be related > to some of the modules you have enabled? > >> >> It's not worth me spending time on since I have other PHP build >> issues that are far more important like why 5.2.3 wont generate a >> thread safe binary for apache 1.3.33 or the binaries are thread >> safe and the modules aren't or the reverse (I haven't figured out >> which is the case yet and no one seems to be of any help so far). > > Apache 1 sapi does not need to thread-safe since Apache 1 does not > use threads. > > Ilia Alshanetsky
Further progress, I built for apache 1.3.33 forcing pthreads on, and forced twolevel_namespace (modified configure), then built for apache 2.0.53 using the same cli options (actually I have it scripted) and saved the libphp5.so (as mod_php.apaci-2.0.53.so) and did the same for apache 2.2.4 (as mod_php.apaci-2.2.4.so) and now all the modules except for rar work. rar works for apache 1.3.33 without enabling pthreads and forcing flat_namespace but building as twolevel_namespace it fails (and is the preferred choice for obvious reasons) and while threads aren't used in apache 1.3.33 it doesn't hurt to build with it enabled. In the past I configured for the same on each architecture and then generated a diff of the php_config.h file, then I edited the php_config.h file and added an #if ARCH == ppc / #else / #endif which sets the defines for the architecture and copied this over before the make command so it generates a universal binary that doesn't segfault and doesn't suffer the date "Balloc() error" issue. As well, Ive been generating a very free substitute to the $9K ADE (yes I was one of the dumb ones who actually bought it thinking it was a gotta have deal) out of a 10.4.3 universal OSX installer DVD that allows me to build in a clean environment (and isn't married to any particular hardware) that isn't tainted by software installs. The only real differences is that the ADE is universal starting at 10.4.0 and offers the greatest compatibility and the free is at 10.4.3 and I've only encountered a rare issue where the 10.4.3 build wouldn't work in a 10.4.0 environment due to a required symbol in libSystem.B.dylib that is referenced from the Carbon.framework that isn't available below 10.4.3, if you have to link against Carbon or ApplicationServices frameworks then try to run below 10.4.3 then it's a no-go. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFGzlu+0hzWbkf0eKgRAjmLAKCUvSgwLMc+zCHV2FOSUd75FW6oFQCeMaHI RRheBzAVX95R1mmAKjC+NcA= =XM3t -----END PGP SIGNATURE-----

Edin Kadribasic

19 years ago
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The windows build is ready for download at: http://downloads.php.net/edink/php-5.2.4RC3-Win32.zip http://downloads.php.net/edink/php-5.2.4RC3-win32-installer.msi http://downloads.php.net/edink/pecl-5.2.4RC3-Win32.zip http://downloads.php.net/edink/php-debug-pack-5.2.4RC3-Win32.zip Edin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGzru+oL7jghV9D6gRAimCAJ9wZvjlg9NoHS/LjBRE2defv8XIBQCgkdSg 1OHTDc9LD3NH6G7hIm/Qogc= =nEMq -----END PGP SIGNATURE-----