Subject: Re: groff from today
To: None <firstname.lastname@example.org>
From: Chris Gilbert <email@example.com>
Date: 10/01/2003 09:52:56
On Wed, 1 Oct 2003 00:35:18 -0600 (MDT)
Rick Kelly <firstname.lastname@example.org> wrote:
> Andrew Brown said:
> >>div.o(.rodata+0x5f4): undefined reference to `__pure_virtual'
> >>div.o(.rodata+0x5f8): undefined reference to `__pure_virtual'
> >>div.o(.rodata+0x5fc): undefined reference to `__pure_virtual'
> >>div.o(.rodata+0x600): more undefined references to `__pure_virtual'
> >you don't, by any chance, have half a build installed (ie, a build
> >that died before completing), do you?
> I don't believe so. Where does `__pure_virtual' come from?
> >i hit this about two weeks ago or so on my sparc. i worked around it
> >by replacing the contents of /usr/include and /usr/lib with something
> >not quite so new. the problem seems to be in libstdc++.so.5 or
> I've now got 2 -current machines that won't build.
> 1. i386. Userland is from 1.6P era, around 3/2003, just before the SA
> went in. Groff configure thinks the c++ compiler doesn't work
> 2. i386. SMP. Successful build on 9/9/2003. Compile now dying in groff
> due to `__pure_virtual'.
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?