[omniORB] omniORB 2.5.0 and shared application libraries

[Sai-Lai Lo]

Despite of what Sun has said (or not said) about the compatiability of
Solaris 2.5 and 2.6 binaries, we found that using Solaris 2.5 binaries (may
be just the shared libraries) on Solaris 2.6 is problematic.

I recommend you recompile the omniORB distribution native on Solaris 2.6.
Or better just download the new omniORB 2.6.0 binaries for Solaris 2.6.

Regards,

Sai-Lai


>>>>> Tim Barbour writes:

> Is there any known problem with omniORB 2.5.0 developing applications
> that use shared libraries ? Is omniORB2 generally known to work with
> applications that contain shared libraries ?

> We have several applications that run fine with static libraries.
> Recently (very recently) we tried building them with shared libraries.
> The resulting applications run, but when the client calls an operation
> on the remote server interface, a CORBA::SystemException is thrown
> (apparently in the client). The details are:

> completed()=1
> minor()=0
> NP_RepositoryId()=IDL:omg.org/CORBA/BAD_OPERATION

> We are using SunOS 5.6, Sun CC 4.2 and the ORL pre-compiled (for SunOS
> 5.5) omniORB 2.5.0 binary. Is it okay to use this omniORB binary with
> SunOS 5.6 ?

> Maybe we have done something lame with the compiler flags for the shared
> libraries, but it's odd that the problem occurs just when invoking a
> CORBA operation.


-- 
Dr. Sai-Lai Lo                          |       Research Scientist
                                        |
E-mail:         S.Lo@orl.co.uk          |       Olivetti & Oracle Research Lab
                                        |       24a Trumpington Street
Tel:            +44 223 343000          |       Cambridge CB2 1QA
Fax:            +44 223 313542          |       ENGLAND