[omniORB] Grief building OmniORB with Mandrake 8

Cay Horstmann cay@horstmann.com
Sun, 15 Jul 2001 10:49:43 -0700


I can't seem to build OmniORB on Mandrake 8. Here is what I do:

1) Untar omniORB_304.tar.gz
2) Set the target to i586_linux_2.0_glibc2.1
3) Set the Python interpreter to /usr/bin/python (which is Python 2.0)
4) make export
5) Build the echo example
6) Run omniNames 
7) Run eg3_impl 
8) Get a CORBA::SystemException

Inserting a few print statements reveals that the offending call is

obj = orb->resolve_initial_references("NameService");

I read the recommendation to install a different compiler. (Mandrake uses
version 2.96, and I think this is not an official Gnu version). So I built
gcc 3.0 and used that. I get exactly the same result.

This is extremely frustrating. I am on a tight deadline updating a book
chapter on interoperating C++ and Java, and have already spent all of the
time allotted for the chapter on building gcc and omniORB. 

What can I do to make progress (other than chose a different ORB)?

- Is there a problem with Python 2.0? (I do get some weird error messages
that Python 1.5.2 or greater is required...)
- Do I need to use any flags when running make export? There is a veiled
threat about threading that I didn't think should apply, but maybe it does?
I don't really have the time to run a large number of 2 hour builds to try
all this out
- Does it pick up any bad shared libraries? I added /usr/local/lib and
/usr/local/omni/lib/i586_linux_2.0_glibc2.1 to LD_LIBRARY_PATH. I am a bit
mystified by the Unix/Linux library loading process and I don't know where
it could pick up undesirable crud. 

When I run with -ORBtraceLevel 25, I get a message
omniORB: throw NO_RESOURCES from initRefs.cc:572
omniORB: Ref to: root<0> -- deleted
just before the exception is caught

Thanks for any help!

Cay


---
Cay S. Horstmann           mailto:cay@horstmann.com
FAX: 1-408-961-8220        http://www.horstmann.com