This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
unsatisfied virtual thunks
- From: Harri Pasanen <harri dot pasanen at trema dot com>
- To: gcc at gnu dot org
- Date: Wed, 12 Dec 2001 15:12:22 +0100
- Subject: unsatisfied virtual thunks
- Organization: Trema Laboratories
- Reply-to: harri dot pasanen at trema dot com
still trying to get omniORB3.0.4 working on HP-UX with gcc version 3.0.3
20011212 (prerelease).
Below, I'm not 100% sure if what I'm seeing below is not my own fault, if so
I'm happy to be corrected. For the time being I am suspecting a gcc bug in
my snapshot.
Thinks seem to compile, but at link time I'm getting unsatisfied symbols:
g++ -o omniNames -g -Wno-unused -Wl,+b,../../../lib/hppa_hpux_11.00_gcc3
-L../../../lib/hppa_hpux_11.00_gcc3 omniNames.o NamingContext_i.o log.o
-lomniORB3 -lomniGK_stub -lomnithread -lpthread
collect2: ld terminated with signal 10 [Bus error]
/usr/ccs/bin/ld: Unsatisfied symbols:
virtual thunk to
CosNaming::_impl_BindingIterator::~_impl_BindingIterator()(first referenced
in NamingContext_i.o) (data)
virtual thunk to PortableServer::ServantBase::_downcast()(first referenced
in NamingContext_i.o) (data)
Couple of things leave me puzzled:
1)
Normally the missing symbols are mangled, but these seem to be the same what
nm -C libomniORB3 gives me, (-C to GNU nm prints out the demangled names).
For example:
00000000 t virtual thunk to
CosNaming::_impl_BindingIterator::~_impl_BindingIterator()
This is using GNU nm 2.11.2, thus binutils 2.11.2.
2)
Why is it refusing to link? Symbols libomniORB3.a look about the same as on
a working version on linux.
Regards,
Harri