If there is anything you should gleam from this article for future reference, Leopard comes with a 64bit Apache installation.

He points out this fact because, if you go and build it as per the normal install instructions, it will toss a "wrong architecture" error. He points out a blog post from Marc Liyanage that helped him understand a bit better. His fix was to run Apache as 32 bit instead of trying to get PHP to compile up to its 64 bit standards. He even includes the two commands you'll need to change Apache over to run this way.

Phalanger is a new PHP implementation introducing the PHP language into the family of compiled .NET languages. [...] Phalanger compiles PHP scripts into MSIL (Microsoft Intermediate Language) which can be executed by .NET or Mono runtime.

He mentions some of the features of the tool (including interoperability between .NET and PHP and the ability to use current PHP libraries inside the .NET application). More information can be found on the Phlanger website.

Anyone crazy enough to help out is more than welcome. I'm currently working on the GTK dependency stack, which will hit quite a few PHP dependencies and PECL extension dependencies in the process. And yes I'd love to submit my hacks/fixes upstream, if someone could find me some information (where do you send libiconv patches?)

Her post mentions some of the things she's already been working on to help further the cause - compiling various Open Source libraries, figuring out issues surrounding MiniGW and some examples of more complex dependency issues she's come across.

I already have ImageMagick installed in my machine and I tried to install the Imagick extension for PHP but I was stuck with strange errors. I have spent couple of hours today to figure out what I did wrong and Why I cant build that extension. Finally I've figured out that I must install ImageMagick from source first to build that extension. Heres how to.

He walks through the install, talking about where to get the package from, where to get the PECL extension for PHP and the compile process (with the result of a .so file PHP's extension can use).

As people keep asking me for an update to my previous benchmarks (PHP / GCC / ICC Benchmark, PHP 5.1 / GCC Benchmark (Update), and PHP 5.1 Performance, I quickly ran a new benchmark today.

He rendered the results out into a series of charts defining the number of total seconds taken for the compile and how long each of the components took. It's impressive to see how much of a jump there was between the 3.0 series and 4.3.

He also includes his compile settings (and machine information) as well as the numbers for the results if you'd like to graph them out yourself.

While Core does ship with a large list of extensions (which are all QA'd and supported by Zend) there are times when you would like to include non-official extensions from PECL for various reasons.

He breaks it down into a few simple steps - download, "phpize" the extension, compile it and add the extension to the php.ini. He details the second step of the process (the phpize) because of some of the differences there are between doing it for a normal PHP install and a Zend Core install.

He also provides directions for an exception to the rule - compiling a PDO driver for your ZC install. You'll have to trick the Zend Core installation into using the right files, though. Full instructions are included.

A user comment made clear that we need to send out a quick status update on how to install / compile mysqlnd with PHP 5.2, 5.3 and 6.0 .

The instructions are only slightly different for each of the version, mainly in the version that's checked out from CVS. The PHP 5.2.x part, however, suggests that you go ahead and make the move to/wait for PHP 5.3 to use the extension. It's still in beta and (probably) won't be included in any of the 5.2.x branches.

I really didn't need to get it running, but the sheer fact that I tried it and it wouldn't work, pissed me off enough to spend some time getting it resolved. Hopefully this helps anyone else having the same problem. I am currently using instant client 11.1, but I did try the 10.2 version with the same results.

He steps through the process he followed - tracking down the missing libaio files, correcting an issue with SELinux loading the Oracle libraries and his realization: he just needed to allow text relocation. Included in the post are the command line calls that'd need to be made to make it all happen.

Over the past week or so I've been figuring out how to compile PHP on Windows, specifically Windows Vista. It's been an interesting ride since I'm not very familiar with compiling on Windows to start with. [...] If you are using Windows Vista, or intend updating/using Visual C++ Express 2008, then my blog entry is largely another coat of sugar on top of Elizabeth's guide to clear up any difference between the two approaches.

He lists the software you'll need to make the compile work (including Virtual Clone Drive, WinRAR, VS 2008 Express and the .NET Framework SDK) and then breaks it down into three steps - the installation of the development environment (and setup), downloading PHP/libraries to the environment and, of course, compiling the PHP instance to your specs (complete with command line calls to make it all happen).

First of all, if you'd rather use the .htaccess than the php.ini capabilities of a phpsuexec environment, then shame on you. But, we have some customers who are terrified of php.ini and would rather use the .htaccess. So what? Ok, well there is a workaround.

The connecting piece is the htscanner extension - she includes installation instructions and how to include it into your PHP installation (as well as how to set the PHP values in the .htaccess).