Re: Apache 1.3.26?

> On Tue, 25 Jun 2002, Rasmus Lerdorf wrote: > > > Did you follow the INSTALL file instructions carefully step by step? If > > so, where are things going wrong? > > Yes indeed. > > Where things go wrong depends heavily upon which method I use to compile > PHP... > > If I use --with-apxs, I am able to produce a libmodphp4.so (or something > of that nature). When I start Apache, it complains that the API used by > the .so is 'strange', and refuses to load it. libmodphp4.so? It should be libphp4.so, not libmodphp4.so Make sure you do a make clean, rm config.cache and try the apxs method again. It works for millions of PHP sites out there. Yours is not going to be any different. > If I use --with-apache, and point it to the Apache source directory, I > have to go through some Hurculean tasks to get apache to compile (mainly > because includes and libraries that are needed when compiling in the PHP > module aren't in the Makefiles..., and I have to modify mod_php.c > because for some reason Apache wants the object to be named > modphp_module, rather than php_module *sigh* )... Uh, no, you are completely misunderstanding something. Exact error messages are required here. > Anyway, I am able to get it all compiled, and then I get confused 'cause > there is an 'AddModule modphp_module.c (or something like that) in the > httpd.conf file, but no LoadModule (which I guess is good since this > approach didn't produce an 'so' file. However, when I start Apache I get > an error saying that the module can't be added because there is no > 'LoadModule' directive. Again, this is explained in the INSTALL file. When using --with-apache you are building PHP statically into your httpd binary, so there is no LoadModule needed and certainly no libphp4.so is created. The module is already in there. > Sooo... that's the long story. I'd like to use 4.2.1, but I can't see > how. Please please please, sit down and quietly read through the INSTALL file a couple of times. -Rasmus