[omniORB] Problems building OmniOrb on AIX 4.1.5

[Duncan Grisby]

On Wednesday 14 March, vasudha.govindan@westerngeco.com wrote:

> I am having problems building OmniOrb 3 on AIX 4.1.5 using IBM C Set++
> 3.1.4.

[...]
>      -p../../../src/lib/omniORB2  -ComniORB3 ../../../idl/Naming.idl
>      ../../../bin/powerpc_aix_4.2/omniidl[32]: 34646 Killed
>      gmake[2]: *** [omniORB3/Naming.hh] Error 137

The "Killed" makes it look like some other process killed omniidl, but
that seems unlikely. I guess it must have segfaulted or something, so
the OS killed it.

> Seems like omniidl is not built right. I get the following error when I
> build the examples/echo directory:
> 
>      ../../../bin/powerpc_aix_4.2/omniidl -bcxx -Wba -Wbtp -C../../stub
> echo.idl
>      omniidl: Could not import back-end 'cxx'
>      omniidl: Maybe you need to use '-p' option?
>      omniidl: (the error was 'No module named cxx')

That's not the same problem, since the cxx module hasn't yet been
installed, at the stage your compile died. Try running just

  ../../../bin/powerpc_aix_4.2/omniidl echo.idl

That won't try to generate any code, but it'll run the front-end.
Determining whether that works will help track down the problem.

> I have a working Python 2.0. However, I could get Python to work only with
> the "no-threads" option. So, I have a non-threaded Python but it seems to
> be working fine and passes all the test suites.

omniidl doesn't need threads in Python, so you should be OK on that
score. If you want to use omniORBpy, you'll definitely need to build a
multi-threaded Python.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --