|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #54433 API Module differences should show actual module paths.
Submitted: 2011-03-31 15:14 UTC Modified: -
Avg. Score:3.0 ± 0.0
Reproduced:0 of 0 (0.0%)
From: RQuadling at GMail dot com Assigned:
Status: Open Package: *Configuration Issues
PHP Version: 5.3SVN-2011-03-31 (snap) OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
12 + 11 = ?
Subscribe to this entry?

 [2011-03-31 15:14 UTC] RQuadling at GMail dot com

If a user has mixed the versions of the extensions and PHP, the presence of a 
physical filepath for the extensions and php in the resulting error message 
would help identify the problem quicker.

I've created a small patch to ext/standard/dl.c which simply appends the path of 
the extension and the sapi_module.executable_location to the lines detailing the 
conflicting API numbers.

This isn't a complete fix as the sapi_module.executable_location may not be 
fully valid in all circumstances (see

Copy an inappropriate module into the extension folder.

Running ...

C:\php5\php.exe -dextension=php_soap.dll -ddisplay_startup_errors=1 -m

outputs ...

Warning: PHP Startup: soap : Unable to initialize module
Module compiled with module API=20060613 (C:\PHP5\ext\php_soap.dll)
PHP    compiled with module API=20090626 (C:\PHP5\php.exe)
These options need to match
 in Unknown on line 0


API_Module_Differences (last revision 2011-03-31 13:15 UTC by RQuadling at GMail dot com)

Add a Patch

Pull Requests

Add a Pull Request

PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun Feb 25 07:01:28 2024 UTC