>: i'll let you know.  :)
>
>In that case, I wonder if you've still got a stray, old libstdc++ that's
>being picked up during the src/tools compile phase.  This would only affect
>you if you haven't built since the old toolchain and are building right to
>/.

-r--r--r--  1 root  wheel  564092 Nov 14 04:36 /usr/lib/libstdc++.a
-r--r--r--  1 root  wheel  681152 Nov 14 04:36 /usr/lib/libstdc++_p.a
-r--r--r--  1 root  wheel  587218 Nov 14 04:36 /usr/lib/libstdc++_pic.a
-r--r--r--  1 root  wheel  345452 Nov 14 04:36 /usr/lib/libstdc++.so.4.0
lrwxr-xr-x  1 root  wheel      16 Nov 14 04:36 /usr/lib/libstdc++.so.4@ -> libstdc++.so.4.0
lrwxr-xr-x  1 root  wheel      16 Nov 14 04:36 /usr/lib/libstdc++.so@ -> libstdc++.so.4.0

if anything, the older one would have been from 9/21.

>In this case, something to try is to build and install with MKMAN=no set in
>mk.conf or the environment, and then try doing a cleandir and rebuild in
>src/tools/groff and build everything with manpages.

i'll try that if the current build dies the same way.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."