By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,633 Members | 1,735 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,633 IT Pros & Developers. It's quick & easy.

Binary incompalibilities in PHP extensions

P: n/a
A client of mine reported the following error message that occurred
whilst trying to load a third-party PHP extension through PHP v4.1.1
(running under Apache v1.3/Windows XP). The module was originally
compiled using the v4.2.3 code base.

===
Module compiled with module API=20020429, debug=0, thread-safety=1
PHP compiled with module API=20010901, debug=0, thread-safety=1
===

I thought binary incompatibilities (with respect to extensions) only
occurred across major PHP version upgrades (e.g. v3 -> v4).

Does anyone know of a list of critical PHP version upgrades at which
point it is necessary to rebuild PHP extensions ?

There appear to be plenty of references to problems of this nature in
the various PHP support forums but no clear directives with regards how
to avoid these compatibility issues in the first place.

Thanks in advance !
--
----------------------------------------------------------
Chris Munt
ITA Consulting Ltd
M/Gateway Developments Ltd : http://www.mgateway.tzo.com
Royal Marsden NHS Trust : http://www.royalmarsden.org
----------------------------------------------------------
Jul 17 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.