[omniORB] [omniORB]not able to run omniidl

[Mohan]

I am sorry for the mistake I am using gcc compiler version 2.95.3 under sun
sparc solaris v 5.8. But still I am getting errors when I run omniidl after
building and installing omni as explained in the readme.unix file.
But I am not quite understood the following information

"If you are using gcc or the default compiler for your platform is
gcc, it is most likely that you have to edit the CXX and CC make
variables in the platform file. Moreover, only the most recent
versions of gcc, i.e. egcs-1.1.2 and gcc-2.95 has proper support for
multithreaded exception handling. Moreover, the gcc compiler has to
be configured with the --enable-threads option or else the code
generated would not work reliably. The default version of gcc
compiler that comes with your platform may not be the right version"

Where exactly I have to use --enable-threads option? When I build the souce
I didnt specify any where(or I couldnt find this option) in the .mk files.
Is this the reason for not able to run the executable properly.

Thanks,
Ram
----- Original Message -----
From: "Bruce Fountain" <fountainb@switch.aust.com>
To: "Mohan" <rmohan@ice-com.com>
Sent: Thursday, August 01, 2002 9:54 AM
Subject: Re: [omniORB] [omniORB]not able to run omniidl


> On Thursday 01 August 2002 12:17, Mohan wrote:
>
> > omniidl: (The error was `ld.so.1:
> > /home/ram/omni/bin/sun4_sosV_5.8/omnipython: fatal: libstdc++.so.2.10.0:
> > open failed: No such file or directory')
> >
> > On .profile I have specified all the required paths where ld.so.1,
> > libstdc++.so.2.10.0 and _omniidlmodule.so existing.
>
> When you say you specified the required path, do you mean the
> LD_LIBRARY_PATH? Set LD_LIBRARY_PATH, export it, then
> source your .profile to pick up the changes.
>
> > I am using the compiler version gcc-2.85 for sparc.
> > Is there any version conflict? What I did was first I unistalled the
> > previous version of gcc which is 3.0 by making use of pkgrm command and
> > installed gcc-2.85-sparc by making use of pkgadd command.
> > Whats going wrong? Can someone help me please?
>
> Not sure why you chose 2.85. That is pretty old. 2.95 is probably
> a better choice if you don't want to go to 3.x.
>
> --
> Bruce Fountain (fountainb@switch.aust.com)
> Senior Software Engineer
> Union Switch and Signal Pty Ltd
> Perth Western Australia
> tel: +618 9256 0083
>