Re: Troubles with -fno-vtable-thunks recompilation.... Was: Strange C++ behaviour

["Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>]

> /usr/local/gcc/lib/gcc-lib/i686-pc-linux-gnu/2.95.1/libstdc++.a(stdstrbufs.o)(.data+0xb4):
> undefined reference to `filebuf virtual table'
> 
[...]
> I assume that I in some way must tell gcc to use the new glibc
> library when compiling new stuff but I am completely lost here.....
> 
> Am I on the right track? Any help would be greatly appreciated!

If vtable thunks are not used, mangling of the vtable changes: It
either starts with '__vt.' or '__vt_'. It appears that libstdc++
requires a different symbol than you have available.

This, in turn, could result from an incorrect contents of _G_config.h,
which explains the C++ vtable mechanism to C applications. You'll
probably have numerous copies of a file with that name. Make sure you
are using the right one consistently. The one that comes with glibc is
probably wrong if you are not using vtable thunks and needs to be
replaced.

Regards,
Martin