Compiling PECL extensions statically into PHP

To statically include the extension within the PHP build, put the extensions source into the ext/ directory found in the PHP source. For example:

$ cd /your/phpsrcdir/ext $ pear download extname $ gzip -d < extname.tgz | tar -xvf - $ mv extname-x.x.x extname $ rm package.xml

This will result in the following directory:

/your/phpsrcdir/ext/extname

From here, build PHP as normal:

$ cd /your/phpsrcdir $ ./buildconf --force $ ./configure --help $ ./configure --with-extname --enable-someotherext --with-foobar $ make $ make install

Note: To run the 'buildconf' script you need autoconf 2.13 and automake 1.4+ (newer versions of autoconf may work, but are not supported).

Whether --enable-extname or --with-extname is used depends on the extension. Typically an extension that does not require external libraries uses --enable. To be sure, run the following after buildconf:

$ ./configure --help | grep extname

User Contributed Notes
Compiling PECL extensions statically into PHP

sibaz at sibaz dot com
07-Apr-2005 09:50


./buildconf --force 

will fail to rebuild configure if the date of the files in your extension are older than the current build files (quite likely if you're trying to build an old extension)

To get round this, use 

tar -xzmf extname.tgz

(x to extract, z because its a gzipped archive and m to give all new files the current date)

or as the instructions say :-

gzip -d < extname.tgz | tar -xmvf -

search for in the