weird buildworld consequences in 6.0

[David Coder]

oh, i forgot to add:  i've got COMPAT_FREEBSD5 enabled in my kernel.
 
On Sat, 28 Jan 2006, David Coder wrote:

:Date: Sat, 28 Jan 2006 16:24:49 -0500 (EST)
:From: David Coder <dacoder at dcoder.net>
:To: freebsd-stable at freebsd.org
:Subject: weird buildworld consequences in 6.0
:
:
:i've an up-to-date 5.4 system that i'd like to upgrade to 6.0 to take
:advantage of the improved SMP but keep running into the following, using
:pristine 6.0 sources & (as far as i can see) following the UPDATING advice
:scrupulously, namely that after running make buildworld & make kernel, using
:the 5.4 ldd gives me either:
:
:# ldd /usr/obj/usr/src_6/bin/sh/sh
:/usr/obj/usr/src_6/bin/sh/sh:
:        libedit.so.5 => /lib/libedit.so.5 (0x2809c000)
:        libncurses.so.6 => /lib/libncurses.so.6 (0x280b2000)
:        libc.so.6 => /usr/local/lib/pluginwrapper/flash6.so (0x280f5000)
:
:when i try to boot into single-user to install world; and the 6.0 ldd gives me
:
:# pwd
:/usr/obj/usr/src_6/usr.bin/ldd
:# ./ldd ../../bin/sh/sh
:/libexec/ld-elf.so.1: Undefined symbol "__stdoutp" referenced from COPY
:relocation in ./ldd
:
:which i sometimes also get, & that doesn't work very well, either.
:
:anybody got a clue what i'm doing wrong?
:
:thx.
:
:===========
:David Coder
:Consulting Network Engineer
:Washington, DC
: