Jump to content

How do I use the right PHP version to compile my Sphinx PECL extension?


Recommended Posts

Recently I installed the Zend Server 5 trial (PHP 5.3). Now I'm trying to include the Sphinx PECL extension in my Zend Server install.

 

I've followed their steps to rebuild the extension (I still have the PECL extension download on my Ubuntu server) but I'm still seeing the following error when trying to start Apache.

 

[21-Jul-2010 18:30:37] PHP Warning:  PHP Startup: sphinx: Unable to initialize module
Module compiled with module API=20060613
PHP    compiled with module API=20090626
These options need to match
in Unknown on line 0

 

Here's what I'm running:

 

/tmp/pear/cache/sphinx-1.0.4# /usr/local/zend/bin/phpize
Configuring for:
PHP Api Version:         20090626
Zend Module Api No:      20090626
Zend Extension Api No:   220090626

/tmp/pear/cache/sphinx-1.0.4# ./configure --with-php-config=/usr/local/zend/bin/php-config

/tmp/pear/cache/sphinx-1.0.4# make

/tmp/pear/cache/sphinx-1.0.4# make install
Installing shared extensions:     //usr/local/zend/lib/php_extensions/

 

But the resulting module still seems to be compiled with 20060613.

 

Could this be because the original install of PHP 5.2 is on the server? Or would the "--with-php-config" switch on the 'configure' work around that?

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.