Re: imap shared with a different openssl path

From:	Brian J. France	Date:	Sun, 01 May 2005 04:41:38 +0000
Subject:	Re: imap shared with a different openssl path
References:	1 2 3	Groups:	php.internals
Request:	Send a blank email to internals+get-16156@lists.php.net to get a copy of this message

On Apr 29, 2005, at 5:33 PM, Edin Kadribasic wrote:

I don't know if this would break anything or not, thoughts?
You should tell at least what version of PHP you're using. Or even better: create a bug report at bugs.php.net and don't forget to fill up all the fields required.
Not every extension can be built by running phpize in its directory due to external dependencies. What's wrong with building it from php source root with ./configure --with-imap=shared ?

I will try that on Monday, but my guess is it will then force PHP to be linked with openssl (either via --with-imap-ssl=<path> or having to set --openssl-dir=<path>). This would be another problem as we don't want PHP linked with openssl for other reasons, like having to build/maintain/support two versions (0.9.7 and 0.9.6). Yes, we know without linking openssl secure streams don't work and we have no problem with that. Brian