On Fri, 14 Feb 2003, Steve Bellovin wrote:

> Using build.sh kernel=... I get this:
>
> cc  -O -o nbmake *.o
> ===> DESTDIR path:
> ===> TOOLDIR path: /usr/src/tools/obj/tools.NetBSD-1.6M-i386
> ===> Created /usr/src/tools/obj/tools.NetBSD-1.6M-i386/bin/nbmake
> ===> Updated /usr/src/tools/obj/tools.NetBSD-1.6M-i386/bin/nbmake-i386
> ===> Building kernel without building new tools
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
----->>||||||||||||||||||||||||||||||||||||||||||
> ===> Building kernel CHALLENGER.acpi
> ===> Kernel build directory: /usr/src/sys/arch/i386/compile/obj/CHALLENGER.acpi
> rm -f a.out [Ee]rrs mklog core *.core .gdbinit
> /usr/src/sys/dev/ata/files.ata:17: syntax error
> /usr/src/sys/dev/ata/files.ata:21: undefined attribute `ataraid'
> /usr/src/sys/arch/i386/conf/files.i386: device `ataraid' used but not defined
> *** Stop.
>
> ERROR: nbconfig failed for CHALLENGER.acpi
> *** BUILD ABORTED ***
>
> I assume I need a new config; I would think, though, that the toolchain
> would ((make that "should") do that for me,

Clearly, it does not. Try, instead, "./build.sh tools kernel=...".

> given the usual warnings
> about not running a new userland without first upgrading the kernel.

The toolchain is not userland, it's all host tools, compiled against
your running system. You could build a full release (to a $DESTDIR),
without rebooting from a new kernel at all, just don't try to run any
of it without updating the kernel.

Frederick