[omniORB] How to build OmniORB under linux Alpha ?

Raffort, Thomas Thomas.Raffort@Compaq.com
Fri, 8 Feb 2002 15:40:16 +0100


Duncan,

For gcc3, I think the --enable-threads option is supported.
(http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/howto.html#3).
So if the C/C++ libraries are build again with gcc3 and =20
the --enable-threads option, I think it will be possible=20
to build and to use OmniORB under Linux Alpha 7.1.
I will try it as soon as the Alpha RedHat 7.2 will be released.
(I hope the lib in this release will be well build for multi-
thread app.)
Any comments welcome.

Regards.
Thomas.

-----Original Message-----
From: Duncan Grisby [mailto:dgrisby@uk.research.att.com]
Sent: mercredi 6 fevrier 2002 23:58
To: Raffort, Thomas
Cc: omniorb-list@uk.research.att.com
Subject: Re: [omniORB] How to build OmniORB under linux Alpha ?=20


On Wednesday 6 February, "Raffort, Thomas" wrote:

> Have you got more information on this issue ?
> We will see if we can do something...

Now I come to look, I see that perhaps it has been fixed in gcc 3.  If
you look at

  http://gcc.gnu.org/install/specific.html#alpha*-*-*

you'll see that in the Tru64/OSF section, it says that gcc does not
support --enable-threads. It used to be the case that it was not
supported on Linux either, and I can't see anything in the release
notes to say that it was added in gcc 3.

The documentation for Compaq's C++ compiler for Linux says that the
libraries are not thread safe, and I'm pretty certain that that
relates to exception handling code too.

Regardless of whether exception handling works or not, the build
should work OK. I think the thing about clashes with gcc naming are
harmless, and due to conflicts between the new gcc name mangling
scheme and some of the generated names omniORB uses. I don't think the
clashes ever actually break anything.

The problem with the libCOS.so is probably because the Alpha Linux
platform files don't have details about how to build a shared library,
since the platform is considered broken. It shouldn't be hard to fix
that.

I'm away at the moment. I'll have another, proper, look at this next
week when I'm back in Cambridge.

Cheers,

Duncan.

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