ID: 23906
Comment by: joho at webbplatsen dot se
Reported By: mbrennen at fni dot com
Status: No Feedback
Bug Type: IMAP related
Operating System: MDK 8.2 (Linux 2.4)
PHP Version: 4.3.2
New Comment:
I have a problem similar in nature, but it gets caught slightly earlier
than at Apache start-up. If I enable --with-imap and/or
--with-imap-ssl, the CLI binary of PHP segfaults after "Installing PEAR
environment". If I remove --with-imap* from my ./configure
command-line, things are hunky dory. This is on a SUSE 8.1 (2.4)
machine, with the imap2001a-devel/lib RPMs from the SUSE distribution.
Previous Comments:
------------------------------------------------------------------------
[2003-06-26 18:20:25] [EMAIL PROTECTED]
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
------------------------------------------------------------------------
[2003-06-15 17:49:44] [EMAIL PROTECTED]
Can you please try reducing the configure options to only contain the
apache and imap related options?
And also try compiling PHP as DSO.
------------------------------------------------------------------------
[2003-06-06 19:12:59] mbrennen at fni dot com
As originally stated, 4.3.0 runs with --with-imap-ssl; 4.3.2 segfaults
on startup with that option, all other things being equal. Why is that
NOT a bug?
I see no reason why you keep classifying the bug as bogus. I am very
open to hearing why this is not a 4.3.2 bug, but the reason must be
valid. Your claim that IMAP was built without SSL support is not true.
------------------------------------------------------------------------
[2003-06-06 18:43:26] [EMAIL PROTECTED]
If it works without --with-imap-ssl, what is the problem?
------------------------------------------------------------------------
[2003-06-06 10:51:55] mbrennen at fni dot com
The c-client is built with SSL support. There are two MDK 8.2 IMAP
RPMs installed on the server.
imap-2001a-5.1mdk
imap-devel-2001a-5.1mdk
Running 'strings /usr/lib/libc-client.a' I see references to ssl_open,
ssl_aopen, ssl_getline, ssl_getbuffer and other ssl functions. There
is also a libc-client-nossl.a library. It seems safe to assume that the
libc-client.a I am linking against was built with SSL support. Do you
disagree?
Why did the --with-imap-ssl configuration work without problem on 4.3.0
on exactly the same server, with the same RPM set?
Is there perhaps an openssl version dependency change between 4.3.0 and
4.3.2? The following SSL RPMs are installed. Does 4.3.2 depend on a
later version?
libopenssl0-devel-0.9.6i-1.4mdk
openssl-0.9.6i-1.4mdk
libopenssl0-0.9.6i-1.4mdk
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/23906
--
Edit this bug report at http://bugs.php.net/?id=23906&edit=1
