I had the same problem.
But as I think, it is just some safety system, because nobody says that
modules from one version must fit to the others. Sometimes the changes in
next versions are too deep.
The ZEND_MODULE_API_NO parameter is defined in Zend/modules.h and
is checked for example in dl function (see ext/standard/dl.c).
As I can see, there're no means to switch it off by a siple #define
or something.
So the best solution is just to recompile.
On 17 Jan 2001 [EMAIL PROTECTED] wrote:
> From: [EMAIL PROTECTED]
> Operating system: Windows 2000
> PHP version: 4.0.4
> PHP Bug Type: Dynamic loading
> Bug description: Module compiled with 4.0.3 don't run with 4.0.4 and v.v.
>
> When calling in PHP 4.0.4 a module developed with PHP 4.0.3, I get the
> following message:
>
> hostware: Unable to initialize module
> Module compiled with debug=0, thread-safety=1 module API=20000809
> PHP compiled with debug=0, thread-safety=1 module API=20001214
> These options need to match
>
> When I recompile the module, it works. But loading the newly compiled module
> with older PHP 4.0.3, I get a similar message.
>
> I would like to use my module in any PHP version.
>
>
> This is my module declaration:
>
> zend_module_entry php_hostware_module_entry =
> {
> "hostware",
> php_hostware_functions,
> PHP_MINIT(hostware),
> PHP_MSHUTDOWN(hostware),
> NULL,
> NULL,
> PHP_MINFO(hostware),
> STANDARD_MODULE_PROPERTIES
> };
>
> Possibly the key is the word STANDARD_MODULE_PROPERTIES, which has
> ZEND_MODULE_API_NO in it.
>
>
> Thank You for Your help.
> Joacim Zschimmer
>
>
>
>
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
