[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] PHP 4.05 on SuSE
- Subject: [ale] PHP 4.05 on SuSE
- From: eric.ayers at mindspring.com (Eric Z. Ayers)
- Date: Tue, 22 May 2001 04:55:56 -0400
I had the same problem.
1) you may need to comment out one of your old mime types for .php that
marks it as a PHP3 page.
2) There is a big warning that comes out when you compile PHP as an
apache module about conflicts with mysql between other apache modules.
I suspect that this is what caused the problem.
Try commenting out the lines in httpd.conf that pertain to PHP3 and
anything else that might be linked against mysql and then see if your
PHP4 module loads. This is what worked for me.
This is as far as I got in solving the problem. PHP4 pages work, PHP3
pages do not. I suspect that the solution is to install the mysql
shared library (libmysql.so?) and then recompile the PHP4 module (and
probably the PHP3 module as well) with the argument
--with-mysql=<path_to_mysql_installation> they might be able to co-exist.
Josh Freeman wrote:
> Does anyone have any experience setting up PHP 4.05 as an apache
> module on SuSE, probably version 7.0? I got it working relatively
> easily on SuSE7.1, but the same tricks aren't working on 7.0. Here's
> what I've done so far:
> ../configure --with-mysql --with-apxs --with-pgsql
> make install
> The --with-apxs switch adds the followng line to httpd.conf:
> LoadModule php4_module /usr/lib/apache/libphp4.so
> There is no corresponding AddModule line, however.
> I also have the mime types set up, but whenever I go to a page that
> has the phpinfo() tag, it reports back that I am still using php 3.0.
> Yes, I still have php3 still loaded, as I think that both can coexist
> on the same server.
> Any ideas?
> Thanks in advance.
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.