Coredumps/Different binary for handler

I'm running FreeBSD with apache20, php5 and SUEXEC. There are two
problems that I have. The first one is with php-cli giving errors and
creating coredumps because of the output you can see below. As far as
I've managed to find out it is something that can't be fixed, but any
solutions are welcome

-----
PHP Warning: PHP Startup: mysqli: Unable to initialize module
Module compiled with module API=20060613, debug=0, thread-safety=0
PHP compiled with module API=20050922, debug=0, thread-safety=0
These options need to match
in Unknown on line 0
-----

The second problem that I have is when I update php5 and it is
installed I can't visit PHP pages anymore. I can fix this by copying /
usr/local/bin/php-cgi to /usr/local/bin/php. The question that I have
is if it is possible to just make apache use a different binary than
the default.

If anybody know the solution to either problem I would appreciate it
greatly as these problems have been bugging me for a long time.

Re: Coredumps/Different binary for handler

Post removed (X-No-Archive: yes)

Re: Coredumps/Different binary for handler

On Dec 27, 12:41 pm, Davide Bianchi
wrote:
> On 2007-12-27, ruud.althui...@gmail.com wrote:
>
> > PHP Warning: PHP Startup: mysqli: Unable to initialize module
>
> Your PHP ain't compiled with mysqli or is not compiled correctly.
The last thing is the problem, I believe FreeBSD is the fault of that.
See the API versions.

> > The second problem that I have is when I update php5 and it is
> > installed I can't visit PHP pages anymore.
>
> Your php configuration is not updating correctly or is expecting the
> executable in a different position.
The executable exists, it just won't use it.

> > The question that I have is if it is possible to just make apache use
> > a different binary than the default.
>
> Apache doesn't know anything about PHP, it either run the php dso module
> to execute the code or it runs the cli executable indicated in the
> script. Fix those.
I believe i found the problem with your comment about what binary it
uses. I have a patched SUEXEC that has the binary hard coded, I just
forgot that it is like that.