[omniORB] 2.7.1 and RedHat Linux 6.0?

Sai-Lai Lo S.Lo@uk.research.att.com
31 Jul 1999 19:48:58 +0100


Well, I've told our sysadmin to stay with RH 5.2. There are 2 issues with
RH 6.0 in relation to program development:

1. gdb on RH6.0 can no longer debug multithreaded programs (omniORB2
   programs included).

2. The libc library is glibc-2.1 which is incompatible with glibc-2.0 in RH
   5.2.

   Looks like RH has created a wrapper library so that binaries compiled on
   RH 5.2 (glibc-2.0) continues to run.

   But if you compile a program on RH 6.0 and link it with libraries
   created on RH 5.2 (glibc-2.0), the executables just core dump.
   For instance, I can't even run a simple hello world when it is compiled
   with egcs (RH 5.2 binary). I believe this is because the hello world
   executable is linked with the stdc++ shared library of egcs (RH 5.2).

   As you can see, it is a mess. You might do better if you have built
   everything from scratch on RH 6.0. 

For us, we stay with RH 5.2 until there is a clear advantage to move on to
glibc-2.1 based system.

Sai-Lai


>>>>> Mike Ladwig writes:

> Has anyone used this combination?  I am trying to move some code from
> 5.2 (where it worked great) to a new RedHat 6.0 (Mandrake) box.  Most
> everything seems to work fine, but an object factory using the
> 'omniORB::loader::set()' functionality aborts without any other comment
> after the return of an object from my loader.

> Thanks for any encouragement or discouragement!


-- 
Sai-Lai Lo                                   S.Lo@uk.research.att.com
AT&T Laboratories Cambridge           WWW:   http://www.uk.research.att.com 
24a Trumpington Street                Tel:   +44 1223 343000
Cambridge CB2 1QA                     Fax:   +44 1223 313542
ENGLAND