ejabberd - Comments for "Compilation fail on ejabberd-2.0.0-RC1" https://www.ejabberd.im/node/2839 en Resolved: I Installed a https://www.ejabberd.im/node/2839#comment-52069 <p>Resolved: I Installed a newer version of Erlang and it worked. For some reason it would not compile under the R10B-10 build.</p> <p>Andy</p> Wed, 26 Mar 2008 21:40:07 +0000 Anonymous comment 52069 at https://www.ejabberd.im Yea the file is installed in https://www.ejabberd.im/node/2839#comment-51934 <p>Yea the file is installed in the correct directory and is on the system. I installed ejabberd 2.0.0 using the binary installation and it worked just fine. The only problem is I'm trying to connect to LDAPS and the only work around now is to update a file and then recompile ejabbered. If anyone else has had this problem let me know.</p> <p>O/S: Linux Enterprise ES4</p> Tue, 04 Mar 2008 23:10:51 +0000 Anonymous comment 51934 at https://www.ejabberd.im Maybe the file SSL-PKIX.hrl is not installed https://www.ejabberd.im/node/2839#comment-51912 <p>So you have Erlang/OTP binaries installed. But ./configure complains that it can't find the file SSL-PKIX.hrl </p> <p>You should check if this file is installed in your system. </p> <p>For example, in Debian unstable, that file is included in the package erlang-dev. And the file is installed in: /usr/lib/erlang/lib/ssl-3.0.12/include/SSL-PKIX.hrl</p> <p>Maybe the location depends in how you installed Erlang/OTP: compiled from source code, using the Debian package, Fedora, Gentoo, ...</p> Sun, 02 Mar 2008 19:41:40 +0000 mfoss comment 51912 at https://www.ejabberd.im I tried what you suggested https://www.ejabberd.im/node/2839#comment-51879 <p>I tried what you suggested and get the same output results as you did for testing if the crypto libraries and ssl are installed correctly. If you could point me in any new directions it would be greatly appreciated. I have 1.1.4 running now but would like to get 2.0.0 up and going :)</p> <p>Thanks in advance<br /> Andy</p> Mon, 25 Feb 2008 21:31:22 +0000 Anonymous comment 51879 at https://www.ejabberd.im Maybe the Erlang ssl library was not compiled https://www.ejabberd.im/node/2839#comment-51867 <p>ejabberd 2.0.0 includes experimental support for Erlang/OTP R12. However, it is required to check in 'configure' if the Erlang version installed in the system is R12 or previous to R12. And it seems that new code added in 'configure' puts you into trouble. </p> <p>The problem is not related to your Erlang version; ejabberd should work correctly with R10B-10. The problem is that you don't have installed the file SSL-PKIX.hrl. </p> <p>I have checked, and SSL-PKIX.hrl is not included in Erlang/OTP R10B-10 source package: it is generated when you compile Erlang. Interestingly, the file ssl_pkix.hrl is included in the source package: that's why you have it in your system.</p> <p>I suspect that most of Erlang was compiled, but not the ssl library. Or it wasn't installed correctly. You tried to compile and install Erlang twice, both with the same problem. Maybe the OpenSSL development files are required but you don't have them?</p> <p>A way to know if the ssl and crypto libraries are installed and can start correctly:</p> <pre>$ erl Erlang (BEAM) emulator version 5.5.5 [source] [async-threads:0] [kernel-poll:false] Eshell V5.5.5 (abort with ^G) 1&gt; ssl:start(). ok 2&gt; crypto:start(). ok 3&gt; q(). ok $</pre> Sun, 24 Feb 2008 19:35:53 +0000 mfoss comment 51867 at https://www.ejabberd.im