[omniORB] omniORB 4.0.2 / omniORBpy 2.2 soon

[Bastiaan Bakker]

On Thu, 2003-07-03 at 17:21, Duncan Grisby wrote:
> I intend to release omniORB 4.0.2 and omniORBpy 2.2 in the next week
> or so. If you have any pending bugs to report, or if you have an
> exotic platform that might have been broken, please try out the
> current CVS contents and let me know of any problems.
> 
> Thanks,
> 
> Duncan.

OK, here's one: 

Summary: (RPM) build failure on RedHat 9. 
Version: CVS snapshot 4.0-latest 2003-07-03.
Symptoms: gcc prints the following errors:

g++ -c -O2 -Wall -Wno-unused -fexceptions -I.. -I./..
-I../../../../../include/omniORB4/internal
-I../../../../../include/omniORB4/internal -D_OMNIORB_SSL_LIBRARY
-D__OMNIORB4__ -I../../../../../stub -D_REENTRANT -I/usr/include -I. -I.
-I../../../../../include -I../../../../../include -D__OSVERSION__=2
-D__linux__ -D__x86__ -o static/sslActive.o sslActive.ccIn file included
from /usr/include/openssl/ssl.h:179,
                 from ../../../../../include/omniORB4/sslContext.h:73,
                 from sslActive.cc:42:
/usr/include/openssl/kssl.h:72:18: krb5.h: No such file or directory
In file included from /usr/include/openssl/ssl.h:179,
                 from ../../../../../include/omniORB4/sslContext.h:73,
                 from sslActive.cc:42:
/usr/include/openssl/kssl.h:132: 'krb5_enctype' is used as a type, but
is not
   defined as a type.
/usr/include/openssl/kssl.h:134: parse error before `*' token
/usr/include/openssl/kssl.h:147: parse error before `*' token
....

Cause: incorrect OpenSSL compile flags. 
OpenSSL on RH9 includes Kerberos support and therefore needs some extra
compile and link options. Preferably these are determined through
pkg-config (and appriopate the M4 macro's):

$ pkg-config --cflags openssl
-I/usr/kerberos/include
$ pkg-config --libs openssl
-L/usr/kerberos/lib -lssl -lcrypto -lresolv -lgssapi_krb5 -lkrb5
-lk5crypto -lcom_err -ldl -lz

Probably the nicest way to handle this is to have ./configure obtain
these values from pkg-config if available and fall back to the old
method otherwise...

Cheers,

Bastiaan Bakker
LifeLine Networks bv