[imp] PHP4 + IMAP + MySQL

[Clive McDowell]

Folks,

in case it's of interest the problem was solved as follows -

1) The mysql.so and imap.so errors were caused by dynamic extensions 
being defined in php.ini when httpd was built statically. PHP3 does 
not report these errors which is what made me believe this was 
causing the problem.

2) Removal of the extensions from php.ini stopped the errors being 
reported but httpd still wasn't reading IMP's php files

3) After some rummaging in the mailing lists I discovered that one 
needs the following 2 lines in httpd.conf to allow both .php and 
.php3 files to be readable via httpd  -

AddType application/x-httpd-php .php
AddType application/x-httpd-php .php3

I could be wrong (having travelled in a couple of circles over the 
last 2 days) but this isn't made entirely clear in the documentation.
Would it be worth adding a couple of lines to the IMP 2.2.3 
installation notes?

Clive McDowell

On Wed, 10 Jan 2001 08:49:57 -0800 Rob Tanner 
<rtanner@cheshire.onlinemac.com> wrote:

> But what bugs me about the error message your getting is that the terminology is 
> all wrong.  The messages should complain about not finding libc-lient.so (which is 
> specifically the UW-IMAP client, and so your library would not likely have the 
> exact same name) and libmysqlclient.so, or something similar, but certainly not 
> ./imap.so and ./mysql.so.
> 
> Would you be willing to share the options you included in the configure script for 
> both apache and PHP?  I'm not at all familiar with imap-2000a, but if you could 
> include the mysql build configuration, that might also be helpful.  Also, did you 
> infact build the imap library and mysql both as dynamic libraries?  Something isn't 
> quite right, and the ld.so.1 errors don't sound to me to be just a path problem.
> 
> I'd certainly try the path solution first because it's easy and it will either 
> resolve the problem (which I doubt) or make it quite that you've got a problem in 
> the build somewhere.
> 
> -- Rob