[jadmin] Openssl RHEL3 openssl configure Warnings

[Scott A]

I recently upgraded Fedora core 3 to Fedora core 5 using the upgrade in place
mechanisms and yes, the removal of libssl.so.4 broke jabberd 1.4.3, so I went
and got the 1.4.4 sources and compiled  it. (./configure --enable-ssl) After
fixing a few version-related sections of the jabber.xml, I noticed that ssl was
not working in the same manner as described below. Furthermore, just for fun I
symlinked libssl.so.0.9.8a (libssl.so.6 is symlinked to this in /lib already) to
libssl.so.4 and ran my old jabberd 1.4.3 binary, which ran executed but ssl
support was broken (for Exodus, Tkabber and SoapBox clients) as well. Did the
API for OpenSSL change enough from 0.9.7a to 0.9.8a to break the existing code
in Jabberd 1.4.x ?

Scott Anderson
sbanderson at impromed.com


> -----Original Message-----
> From: jadmin-bounces at jabber.org 
> [mailto:jadmin-bounces at jabber.org] On Behalf Of Perry, Jeff
> Sent: Wednesday, June 07, 2006 10:00 AM
> To: jadmin at jabber.org
> Subject: [jadmin] Openssl RHEL3 openssl configure Warnings
> 
> I'm having a problem w/ Jabber that keeps SSL support from working.
> Otherwise the install works.  The only thing I've been able 
> to track down is this set of Warnings when I run
> 
> ./configure --enable-idn=/usr/bin/idn --enable-mysql 
> --enable-ldap --enable-ssl --enable-debug 
> --with-extra-include-path=/usr/include/openssl/
> 
> The config finishes and make && make install works but SSL 
> won't work after this.  
> 
> ---Useless OR useful information---
> System is RHEL AS 3r6 patched to current (as of today) Jabber src =
> jabberd-2.0s11 Libidn src = libidn-0.6.3 Mysql =
> MySQL-server-standard-5.0.22-0.rhel3 (with devel, shared, & clients as
> well)
> 
> This is a minimal RHEL install w/ the following rpm packages 
> added up2date -i expat-devel up2date -i gcc cpp glibc-devel 
> glibc-headers glibc-kernheaders up2date -i openssl-devel 
> krb5-devel zlib-devel
> 
> I have openssl installed properly (all the tools work as per 
> usual etc)
> -----
> [root at community root]# rpm -qa | grep ssl
> openssl-0.9.7a-33.17
> openssl-devel-0.9.7a-33.17
> 
> -----configure wierdness (not openssl lines)--- checking if 
> snprintf can handle NULL arguments... yes checking if 
> vsnprintf can handle NULL arguments... yes checking 
> openssl/crypto.h usability... yes checking openssl/crypto.h 
> presence... yes checking for openssl/crypto.h... yes checking 
> for CRYPTO_lock in -lcrypto... yes checking openssl/ssl.h 
> usability... yes checking openssl/ssl.h presence... no
> configure: WARNING: openssl/ssl.h: accepted by the compiler, 
> rejected by the preprocessor!
> configure: WARNING: openssl/ssl.h: proceeding with the 
> compiler's result checking for openssl/ssl.h... yes checking 
> for SSL_connect in -lssl...
> yes checking for OpenSSL version >= 0.9.6b... yes
> --- end explosivo ----
> 
> Has anyone ever seen the WARNING lines in there about openssl?
> 
> Any ideas would be appreciated
> 
> Jeff
> _______________________________________________
> jadmin mailing list
> jadmin at jabber.org
> http://mail.jabber.org/mailman/listinfo/jadmin
> FAQ: http://www.jabber.org/about/jadminfaq.shtml
> _______________________________________________
> _______________________________________________
> jadmin mailing list
> jadmin at jabber.org
> http://mail.jabber.org/mailman/listinfo/jadmin
> FAQ: http://www.jabber.org/about/jadminfaq.shtml
> _______________________________________________
> 


This communication is intellectual property of ImproMed, Inc. All rights to view, reproduce and archive this email are reserved by ImproMed, Inc.