[omniORB] packaging stubs in a dll
Dan Kegel
dank@kegel.com
Tue, 04 Dec 2001 23:20:36 -0800
Nathaniel Smith wrote:
>
> On Tue, Dec 04, 2001 at 04:54:56PM +0100, Renzo Tomaselli wrote:
> > Not so easy as far as data members are concerned (on gcc 2.96), such as
> > typecodes and repoIDs. It seems that order of library feeding into the
> > linker matters a lot, otherwise pointers across shlibs remain (silently)
> > initialized to null, unlike on NT where they remain initialized to garbage.
> > Same mud, different colors ...
>
> I'm not sure if this is the cause of _your_ problem, but you might
> want to consider upgrading your compiler to 2.95 (yes, 2.95 is newer).
> 2.96 never existed, is some Redhat release of a pre-release compiler,
> and has caused various people lots of grief in sometimes strange ways.
> Even if it's not your problem, you might want to consider upgrading
> :-).
>
> See: http://gcc.gnu.org/gcc-2.96.html
In Red Hat's defense, there were valid practical reasons for them to
ship the "2.96" snapshot, and the well-known compatibility
problems only happen when you try to dynamically link to
shared libraries of C++ code compiled by a different compiler,
which the LSB expressly advises you not to do yet.
Fortunately, now that gcc 3.02 is out, the C++ abi is frozen.
By next summer, all the distrols will have switched to
gcc 3.1 or so, omniorb will build properly with it,
peace will reign throughout the planet,
and love will fill the stars.
- Dan
- Dan