[omniORB] omniORB_280 and Sun C++ 5.0

James Riden jamesr@harlequin.co.uk
04 Apr 2000 10:39:55 +0100


"Dr. Uwe C. Hinze" <uhinze@ford.com> writes:
> I cannot compile the following file in
>     omniORB_280src/lib/omniORB2/orbcore
> giopServer.cc,  exception.cc, policy.cc, scavenger.cc, objectRef.cc
> 
> using Sun C++ 5.0 with all new Compiler patches installed using sun4_sosV_5.6.mk
> I get error messages like
> 
> CC -c -O2 -g   -DUsePthread -D_REENTRANT -mt -I. -I./.. -I./../.. -DUSE_omniORB_logStream -D_OMNIORB2_LIBRARY -DUnixArchitecture
> -DCONFIG_DEFAULT_LOCATION='"/etc/omniORB.cfg"' -I.  -I../../../../include -D__sparc__ -D__sunos__ -D__OSVERSION__=5 -o giopServer.o
> giopServer.cc
> "giopServer.cc", line 980: Error: omniORB::MaxMessageSize(unsigned), returning unsigned, was previously declared returning void.
> 1 Error(s) detected.
> or:
> "objectRef.cc", line 827: Error: CORBA::UnMarshalObjRef(const char*, MemBufferedStream&) already had a body defined.
> "objectRef.cc", line 914: Error: CORBA::MarshalObjRef(CORBA::Object*, const char*, unsigned, MemBufferedStream&) already had a body
> defined.

hmm - I saw these errors before I had applied some of the latest
patches. Have you got the list of patches applied handy, and your OS
version ? If Solaris 2.7, do you have the 64-bit support installed ?
(Some people have got it going on Solaris 2.5/2.6 I believe)

cheers,
 James

( disclaimer: mine has got as far as hanging during the compile of
dynSK.cc on Solaris 2.7 )

-- 
James Riden / jamesr@harlequin.co.uk / jamesr@europe.com
"I've suddenly gotten the feeling that GotW #62 has armed me with a very 
large hammer and a nifty pair of nail-tinted glasses."-- Danil on clc++m