R: [omniORB] OmniORB 3.0.4 omniNames problem with Solaris 8/x86 MU4 and GCC 3.0

[Sandro Tolaini]

> I am using a 3.0.3/gcc-2.95.2 omniNames as a workaround. The problem does
> not occur with the omniORB 3.0.4 when compiled with GCC 2.95.2 either. We
> have written a custom load-balancing name server implementation in Python,
> and that works fine also, even when implemented on omniORB 3.0.4/omniORBpy
> 1.4 both compiled with GCC 3.0. Thus, it is highly likely the
> problem is in
> the interaction between omniNames and GCC 3.0 on Solaris 8/x86.

Could you tell me the steps you did to successfully compile omniORB with gcc
(2.95.3) and Solaris 8 x86? I tried but the make process halts with a Python
core dump (SIGABORT) while doing 'omniidl corbaidl.idl'.

I'm using gcc-2.95.3, binutils 2.11.2 and python-2.1, all rebuilt from
sources.

Thanks,
  Sandro.