This is from the 200309090000 snapshot. comp.tgz /usr/lib:

t23: {15} grep __pure_virtual *
Binary file libgcc.a matches
Binary file libgcc_p.a matches
Binary file libgcc_pic.a matches

You'll probably note that /usr/bin/gcc's date is older than several
files in /usr/lib, and perhaps /lib.

I'm quite certain that Andrew Brown's diagnosis is correct: your
libraries and compiler are out of sync. I experienced the same problem,
which only manifested itself when compiling groff. My solution was to
utilize the aforementioned snapshot's /lib and /usr/lib (I didn't have
to touch any headers, but perhaps I got lucky). I just backed up the
old, replaced with the new (well, the new old ;) and after building I
copied over a few necessary older libs.

-Steve

On Wed, 1 Oct 2003 12:41:40 -0600 (MDT)
Rick Kelly <rmk@toad.rmkhome.com> wrote:

> Chris Gilbert said:
> 
> >Are these builds from clean? or an update?  Remember the c++ compiler
> >has changed (to 3.3.1) and this also changed the ABI.  perhaps you've
> >got a mix of old and new .o files?
> 
> Both systems are:
> 
> wolf# gcc -v
> Using builtin specs.
> gcc version 2.95.3 20010315 (release) (NetBSD nb4)
> 
> roothog# gcc -v
> Using builtin specs.
> gcc version 2.95.3 20010315 (release) (NetBSD nb4)
> 
> 
> -- 
> Rick Kelly  rmk@rmkhome.com  www.rmkhome.com