[omniORB] problems building omniORB4 on Solaris with SC 4.2

[Lai, Patrick]

I did a build without -g, and the eg1 example hung on termination:

    $ eg1
    I said, "Hello!".
    The Echo object replied, "Hello!".
    omniORB: Assertion failed.  This indicates a bug in the application
using
    omniORB, or maybe in omniORB itself. e.g. using the ORB after it has
    been shut down.
     file: ../../../../../src/lib/omniORB/orbcore/omniInternal.cc
     line: 659
     info: *pid

With eg2_clt, I got "Caught CORBA::SystemException."  Here's the level 10
trace from eg2_clt:

    omniORB: Distribution date: Sun Sep 22 22:06:56 BST 2002 dgrisby
    omniORB: Information: the omniDynamic library is not linked.
    omniORB: Creating ref to remote: key<0x00000000746f206e000000006c0a>
     target id      : IDL:omg.org/CORBA/Object:1.0
     most derived id: IDL:Echo:1.0
    omniORB: LocateRequest to remote: key<0x00000000746f206e000000006c0a>
    omniORB: AsyncInvoker: thread id = 1 has started. Total threads = 1
    omniORB: throw OBJECT_NOT_EXIST from remoteIdentity.cc:271
(NO,OBJECT_NOT_EXIST_NoMatch)

So it seems that -g would be necessary for the 4.2 compiler too.

-- Patrick

> -----Original Message-----
> From: Duncan Grisby [mailto:duncan@grisby.org]
> Sent: Tuesday, December 17, 2002 10:00 AM
> To: Lai, Patrick
> Cc: 'omniorb-list@omniorb-support.com'
> Subject: Re: [omniORB] problems building omniORB4 on Solaris with SC 4.2
> ...
> > - beforeauto.mk.in
> >   Some flags are apparently missing for Compiler_Sun4.  I copy the
> >   following flags from the Compiler_Sun5 section:
> >     CXXDEBUGFLAGS = -O2 -g
> 
> Do you really need the -g?  That is there to work-around a bug in the
> version 4 compiler, so it shouldn't be needed on version 4. I'll put
> the other things in (and the -g too if it's really required).
> ...