Samuel Liddicott <[EMAIL PROTECTED]> wrote:
I'm running debian testing/unstable based on mepis.
I downloaded the pre-built .deb files, but have also built from source.
My apache2 server reports:
Apache/2.0.52 (Debian GNU/Linux) PHP/4.3.10-2 Midgard/1.6.2/Repository/MultiLang
When the midgard-apache2.so module is loaded, php seems to die when it does a mysql_pconnect. When I don't load unload midhard-apache2.so my php sites work fine.
phpinfo(); works ok, it's just mysql_connect that fails.
Sarge and Sid have MySQL 3.x, 4.0 and 4.1. midgard-php4 compiled against 4.1 was running fine but I decided to compile against 4.0.
any great reason?
php4-mysql is compiled against 3.x cause of some licences issue.
I notice libmidgard.dsc lists build-deps including: libmysqlclient12-dev | libmysqlclient14-dev
But when I do: apt-get build-dep libmidgard
apt tries to remove libmysqlclient14-dev and replace with libmysqlclient12-dev
Further, for libapache2-mod-php4-midgard, only libmysqlclient12-dev is specified
I skipped the "build-dep" and just built against libmysqlclient14-dev (editing the control files).
No joy, though, which puzzles me, now I've broken midgard AND php4, I'll have to go and follow your notes and jigger php instead.
Any idea why it won't build against 14?
What concerns me is that I can't find anything in the php packaging to indicate which versions of the mysql client libs it was build against, and as we see it can be a right pain when two libraries used together need to be using the same mysql client libraries.
Incidentally, wouldn't symbol versioning on the part of the mysql client libs solve this problem? (Sure it might mean two mysql client libs linked to the same application but they ought to work find together)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
