Date: Mon, 17 Jul 1995 08:59:13 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: dufault@hda.com (Peter Dufault) Cc: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: And another g++ question Message-ID: <199507170659.IAA04835@uriah.heep.sax.de> In-Reply-To: <199507162215.SAA04276@hda.com> from "Peter Dufault" at Jul 16, 95 06:15:04 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Peter Dufault wrote: > > > strstream.cc:53: Undefined symbol `__vt$builtinbuf' referenced from text segment > > strstream.cc:59: Undefined symbol `__vt$builtinbuf' referenced from text segment > > strstream.cc:70: Undefined symbol `__vt$builtinbuf' referenced from text segment > > The curious thing is that there is a "__vt$10builtinbuf" defined > in libg++.a but nothing without a 10. Also the undefined is coming > from libg++ .o's, yet the undefineds don't show up in libg++.a > namelist, so it must be some sort of g++ constructed sort of thing. > > Does anyone recognize this problem? Are you sure your C++ compiler and library and header files match? I've typically seen this when installing a new version of g++ on our Data General machines, but it's been a while ago. The __vt$'s are the virtual method tables. There are now two ways (if i recall it right), and one of them is to work without those tables. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507170659.IAA04835>