No, buildkernel is sort of fine- doesn't work for partial trees.
I just missed the UPDATING about a toolchain upgrade. I also figured out how to get myself out of the partial tree mess I was in by dropping back on the ldscript so I could ensure a new kernel prior to building world. > On Mon, Oct 14, 2002 at 08:04:47PM -0700, Matthew Jacob wrote: > > > > Attempts to build kernels today fail for me with: > > > > h ../../../conf/newvers.sh MJCURRENT > > cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs > > -Wstric > > t-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > -fforma > > t-extensions -ansi -g -nostdinc -I- -I. -I../../.. -I../../../dev > > -I../../../co > > ntrib/dev/acpica -I../../../contrib/ipfilter -D_KERNEL -include > > opt_global.h -fn > > o-common -mpreferred-stack-boundary=2 -ffreestanding -Werror vers.c > > linking kernel.debug > > ld: target elf32-i386-freebsd not found > > > > > > > > And these are with i386 systems that are installworld'd within the last > > couple weeks. > > Well, this is what the 'buildkernel' target was invented for (kernel > builds after toolchain upgrades), and why it's the documented standard > way to build kernels after a source upgrade. Do you have this problem > when you use buildkernel? > > Kris > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
