[dovecot] Configure SSL problem
Hi everyone
I have been trying to get Dovecot installed with OpenSSL support, but no matter what I do, when I run Configure, it says "Building with SSL support.........No". I have even tried configure --with-ssl=openssl, to no avail.
I have built and installed OpenSSL, and libssl.so and libcrypto.so are in the /lib directory - what more does Dovecot want? I have tried figuring it out from the Configure script itself but it's cryptic and I am no shell script boffin!
Thanks for any tips
Les
Leslie Viljoen Africa Missions Systems Administrator Cell: 0836186100 Work: 011 6991700 Fax: 011 7945522
On Thu, 2003-03-13 at 11:44, Leslie Viljoen wrote:
I have been trying to get Dovecot installed with OpenSSL support, but no matter what I do, when I run Configure, it says "Building with SSL support.........No". I have even tried configure --with-ssl=openssl, to no avail.
I have built and installed OpenSSL, and libssl.so and libcrypto.so are in the /lib directory - what more does Dovecot want? I have tried figuring it out from the Configure script itself but it's cryptic and I am no shell script boffin!
I assume that you have to change /etc/ld.so.conf or what's its name. And then do a ldconfig.
PS. Can someone make this ml set "Reply-To:" headers? DS.
-- Ian Kumlien pomac@vapor.com
On Thu, Mar 13, 2003 at 01:30:45PM +0100, Ian Kumlien wrote:
PS. Can someone make this ml set "Reply-To:" headers?
I don't think that's generally considered very good behaviour for mailing list. For example it prevents easily replying privately. Some people also prefer to get the replies in private mail as well as to mailing list, which is useful especially with high traffic list.
Setting Mail-Followup-To header (or even reply-to) to mails yourself would help. Of course, that doesn't help if you're accidentally replying privately..
http://www.unicom.com/pw/reply-to-harmful.html http://cr.yp.to/proto/replyto.html
On Thu, 2003-03-13 at 17:07, Timo Sirainen wrote:
On Thu, Mar 13, 2003 at 01:30:45PM +0100, Ian Kumlien wrote:
PS. Can someone make this ml set "Reply-To:" headers?
I don't think that's generally considered very good behaviour for mailing list. For example it prevents easily replying privately. Some people also prefer to get the replies in private mail as well as to mailing list, which is useful especially with high traffic list.
Setting Mail-Followup-To header (or even reply-to) to mails yourself would help. Of course, that doesn't help if you're accidentally replying privately..
http://www.unicom.com/pw/reply-to-harmful.html http://cr.yp.to/proto/replyto.html
Ahhh, I generally saw it in the oposite direction since most ppl could benefit from seeing the "full discussion come to an end".
But, i never know about the reply to all functionality =)
-- Ian Kumlien pomac@vapor.com
On Thu, Mar 13, 2003 at 12:44:52PM +0200, Leslie Viljoen wrote:
I have been trying to get Dovecot installed with OpenSSL support, but no matter what I do, when I run Configure, it says "Building with SSL support.........No". I have even tried configure --with-ssl=openssl, to no avail.
Check config.log what it says about it. Maybe it doesn't find ssl.h.
On Thu, Mar 13, 2003 at 12:44:52PM +0200, Leslie Viljoen wrote:
Hi everyone
I have been trying to get Dovecot installed with OpenSSL support, but no matter what I do, when I run Configure, it says "Building with SSL support.........No". I have even tried configure --with-ssl=openssl, to no avail.
I have built and installed OpenSSL, and libssl.so and libcrypto.so are in the /lib directory - what more does Dovecot want? I have tried figuring it out from the Configure script itself but it's cryptic and I am no shell script boffin!
Did your ssl include files get installed in the fairly standard /usr/local/ssl/include ? If so try something like:
./configure --with-ssl=openssl --includedir=/usr/local/ssl/include
Maybe "configure" could be trained to look there by default..
-mm-
Thanks, I tried this, but it also didn't work.
OpenSSL's .h files are in /usr/local/ssl/include/openssl. I copied all these .h files to /usr/local/ssl/include - and tried both options below - but the configure script still says "Building with SSL support........... no"
The problem seems to stem from: checking for SSL_read in -lssl... (cached) no
My libcrypto.so and libssl.so files are in /usr/local/ssl/lib - this path has been added to /etc/ld.so.conf and I have run ldconfig.
Configure seems to be trying to compile this C file to test the SSL_read function:
#line 7757 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ /* We use char because int might match the return type of a gcc2 builtin and then its argument prototype would still apply. */ char SSL_read();
int main() { SSL_read() ; return 0; }
I can compile this myself if I include -I /usr/local/ssl/include and I replace the "confdefs.h" with "ssl.h".
So I just don't know!
Les
Leslie Viljoen Africa Missions Systems Administrator Cell: 0836186100 Work: 011 6991700 Fax: 011 7945522
"Mark E. Mallett"
<mem@mv.mv.com> To: Leslie Viljoen <Leslie_Viljoen@icoc.org>
Sent by: cc: dovecot@procontrol.fi
dovecot-bounce@pr Subject: [dovecot] Re: Configure SSL problem
ocontrol.fi
2003-03-15 12:29
AM
On Thu, Mar 13, 2003 at 12:44:52PM +0200, Leslie Viljoen wrote:
Hi everyone
I have been trying to get Dovecot installed with OpenSSL support, but no matter what I do, when I run Configure, it says "Building with SSL support.........No". I have even tried configure --with-ssl=openssl, to no avail.
I have built and installed OpenSSL, and libssl.so and libcrypto.so are in the /lib directory - what more does Dovecot want? I have tried figuring it out from the Configure script itself but it's cryptic and I am no shell script boffin!
Did your ssl include files get installed in the fairly standard /usr/local/ssl/include ? If so try something like:
./configure --with-ssl=openssl --includedir=/usr/local/ssl/include
Maybe "configure" could be trained to look there by default..
-mm-
On Mon, 2003-03-17 at 12:46, Leslie Viljoen wrote:
The problem seems to stem from: checking for SSL_read in -lssl... (cached) no
Maybe it's just because of caching. Delete config.cache file.
I can compile this myself if I include -I /usr/local/ssl/include and I replace the "confdefs.h" with "ssl.h".
Also you could try to run:
CPPFLAGS='-I /usr/local/ssl/include/' ./configure
(I don't know if --includedir helps with the configure checks, I should try..)
participants (4)
-
Ian Kumlien
-
Leslie Viljoen
-
Mark E. Mallett
-
Timo Sirainen