PHP 5.3, round 1

PHP 5.3 has hit Alpha 3 now, so it was about time I got around to poking at the new features myself, instead of just glancing over and deleting huge flame wars on the internals list of the minutae of the much, er, ‘discussed’ namespaces implementation.

If you’re running WIndows, they have builds for you, but the rest of us instead get to build from source. This was slightly tricky:

1. get the php sources here:

http://qa.php.net/

2. if you intend to compile in MySQL support, make sure you have some mysql headers and such around. For me on OS X, this got funky as the layout for the mysql5-devel port MacPorts provides does not layout the lib and include directories in the way that the plain-jane PHP sources expect. Luckily I found this post:

http://lists.macosforge.org/pipermail/macports-users/2007-December/00756…

Read the post-extract section of the mysql5 variant of the php5 portfile to see how it copes with this. You just have to make a couple symlinks to make the layout match what php expects. You could:

cd /tmp
mkdir php5mysql5
ln -s /opt/local/lib/mysql5 php5mysql5/lib
ln -s /opt/local/include/mysql5 php5mysql5/include

Then use –with-mysql=/tmp/php5mysql5 in your php configure line instead. Then delete /tmp/php5mysql5 when you’re done.

This got me a build of PHP 5.3 with the plain ol’ mysql extension, but I did run into problems with pdo-mysql. No matter, just mysql will do for testing. Using pecl I installed xdebug, pointed Komodo at the new interpreter and had the basics working.

3. IBM has a great series of articles on the new features:

http://www.ibm.com/developerworks/opensource/library/os-php-5.3new2/inde…

Recent Posts

Webinar - Walking Dead Past Python EOL
Walking Dead Past Python EOL

Stuck living with zombie applications running on Python 2, 3.7 or other past-EOL software? Learn the case for maintaining vs. upgrading, and how you can adopt a culture of getting current and staying current, with lessons from our customers.

Read More
Scroll to Top