-----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-----
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
