Hi all,
I get the following mesage when I start my apache 1.3.27 server:
[warn] Loaded DSO C:/phpdev/php/sapi/php4apache.dll uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI)
Apache/1.3.27 (Win32) PHP/4.3.2 running ...
Apache also pops up error messsage windows:
1. The procedure entry point php_fopen_wrapper could not be located in php4ts.dll
2. Unknown(): Unable to load dynamic library 'C:/phpdev/php/extensions\php_zlib.dll - The specified procedure could not be found.
These appear three times in succession on each start up.
I recently upgraded to php 4.3.2 and this is when this started, I am only very new to this net hacking stuff so sorry if the solution is obvious!
Any suggestions? (I really don't want to have to recompile from the source if I can help it)
__________________
cheers,
Brad
apache warning about php4apache.dll; what goes?
Moderator: General Moderators
apache warning about php4apache.dll / EAPI
Hi there,
since no one replied yet: I ran into the same problem after installing
php 4.3.2, and though I am not a programmer, I followed some advice
I found somewhere on the net dealing with "Compiling php4apache.dll
as an EAPI". Indeed the situation described by bradvan is mentioned
on several places but always unanswered as far as I can overlook.
Last week I've gone to a machine that has VC++ 6 installed, installed
the source packages and compiled and double checked the whole thing
several times.
Whatever I did - Apache still claimed all my builds of the php4_module
to be plain Apache API, not EAPI.
The I took a look inside the sources and looked for any occurences of
things like "define EAPI" or "ifdef EAPI" declarations - there are none!
The only occurence of "EAPI" inside the PHP sources is somewhere inside
a readme file where somebody stated that old inherited EAPI stuff was
cleared and removed.
Am I right supposing that we don't need no more to pay attention to
Apache's EAPI warning (which, in turn, should be IMHO turned off on the
PHP side)?
As far as I heard from the news, AC is back in the US, so somebody
should take note of this little problem
Best regards
Ol'man
since no one replied yet: I ran into the same problem after installing
php 4.3.2, and though I am not a programmer, I followed some advice
I found somewhere on the net dealing with "Compiling php4apache.dll
as an EAPI". Indeed the situation described by bradvan is mentioned
on several places but always unanswered as far as I can overlook.
Last week I've gone to a machine that has VC++ 6 installed, installed
the source packages and compiled and double checked the whole thing
several times.
Whatever I did - Apache still claimed all my builds of the php4_module
to be plain Apache API, not EAPI.
The I took a look inside the sources and looked for any occurences of
things like "define EAPI" or "ifdef EAPI" declarations - there are none!
The only occurence of "EAPI" inside the PHP sources is somewhere inside
a readme file where somebody stated that old inherited EAPI stuff was
cleared and removed.
Am I right supposing that we don't need no more to pay attention to
Apache's EAPI warning (which, in turn, should be IMHO turned off on the
PHP side)?
As far as I heard from the news, AC is back in the US, so somebody
should take note of this little problem
Best regards
Ol'man