ejabberd - Comments for "SSL not found during configure"

I have resolved it!

william — Sat, 22 Jul 2006 08:59:42 +0000

I find the directory of openssl headfiles:
In my Debian OS ,that's "/usr/local/ssl/include/openssl",
I don't know why ejabberd can't find this directory,
maybe the openssl in other Linux OS is not in this directory?

so,i executed this:
./configure --with-openssl=/usr/local/ssl/include/openssl

OK!No errors!

Maybe you are the same as me!

I am too in Debian!

william — Sat, 22 Jul 2006 08:18:30 +0000

I am too in Debian!
i have installed the libssl-dev,nothing happened!

More interesting thing is I couldn't install Jabberd too！
The same reason！

i am also having the same

edjil — Wed, 14 Jun 2006 08:20:17 +0000

i am also having the same problem such as yours. i've tried everything you suggested, but nothing works.could someone post a solution on this.thanks

try regenerating the 'configure' script with autoconf

mfoss — Fri, 15 Apr 2005 15:24:43 +0000

I'm starting to think that there's something wrong with the little program used to check SSL_new

You can try to regenerate the 'configure' script from the original 'configure.ac' using Autoconf. Just execute 'autoconf' on ejabberd/src directory.

Me again!

villano — Fri, 15 Apr 2005 14:24:57 +0000

Well I'm writing again because I would like to help others with the same problem, so doing some tests I'm starting to think that there's something wrong with the little program used to check SSL_new because I have been playing with the 'configure' script and I set manually the value yes for the variable have-openssl in order to continue with all the script as if it had detected the openssl package itself. So next thing the configure did was performing a test for the presence and usability of ssl.h; the test was completed succesfully and after that I didn't receive more errors.

Can anyone write a feedback to this thought...

I didn't install openssl binaries!

villano — Thu, 14 Apr 2005 18:22:46 +0000

I have had a lot of work so I haven't done anything about this problem but I was reading again your suggestion and I noticed something important in your words:

If I install only OpenSSL binaries

but I have built openssl from source so I think I have all the libraries but maybe I'm wrong and still need libssl-dev, what do you thing??

./configure --with-openssl already tested!

villano — Wed, 13 Apr 2005 16:23:58 +0000

First of all, thanks for your quick response.

I have tried also ./configure --with-openssl=/usr/local/ssl but I get the same error so I'm going to look for libssl-dev as you suggest and I'll let you know the results.

try ./configure --with-openssl=

mfoss — Wed, 13 Apr 2005 16:16:31 +0000

If I install only OpenSSL binaries, when configuring ejabberd compilation I get:

checking whether build tls... yes
looking for openssl in /usr/local/ssl...
checking for SSL_new in -lssl... no

So it's clear I need to install OpenSSL development files. On Debian, I do:

apt-get install libssl-dev

And now I get:

checking whether build tls... yes
looking for openssl in /usr/local/ssl...
checking for SSL_new in -lssl... yes

You are probably missing some files, or they are not placed where configure is looking for them.

Since you really want SSL, STARTTLS and SASL, disabling this feature is not a good idea. Try

./configure --with-openssl=/usr/local/ssl

or similar, and comment here if it works, so other people can benefit from your experience.

I'm running SCO 5.0.5

Interesting, this is the first time I read someone tries to install ejabberd on SCO Unix. Once you have succesfully installed it, could you please comment here if it works well or not? Thanks.