That problem happens when -T is not used and you are using a newer kernel
than your toolchain, to avoid this I'd suggest you to use -T in the future.

I agree that build.sh must be smarter.


----- Original Message ----- 
From: "Jeremy C. Reed" <reed@reedmedia.net>
To: <current-users@netbsd.org>
Sent: Thursday, April 05, 2007 10:27 PM
Subject: No nonexistent/bin/nbmake, needs building.


>I used ./build.sh -U tools kernel=JCR20070405
> and it failed later due to some kernel option problems. (So I fixed.)
>
> Then I ran:
>
> ./build.sh -U kernel=JCR20070405
>
> and it did:
>
> glacier:/usr/src$ ./build.sh -U kernel=JCR20070405
> ===> build.sh command: ./build.sh -U kernel=JCR20070405
> ===> build.sh started: Thu Apr  5 15:18:58 CDT 2007
> ===> NetBSD version:   4.99.16
> ===> MACHINE:          i386
> ===> MACHINE_ARCH:     i386
> ===> Build platform:   NetBSD 3.99.24 i386
> ===> HOST_SH:          /bin/sh
> ===> No nonexistent/bin/nbmake, needs building.
> ===> Bootstrapping nbmake
> checking for sh... /bin/sh
> checking for gcc... cc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for executable suffix...
> checking for object suffix... o
> ...
> ^C
>
>
> I looked in the BUILDING file about nbmake. But still this is unclear.
> And I have had this problem before (and reported it before I think).
>
> What is the purpose of rebuilding make over and over again?
>
> In fact, I don't want any tools made as I am running current and building
> a current kernel. It is a waste of time.
>
> I also tried:
>
> ./build.sh -U -T tools kernel=JCR20070405
>
> But same problem. (I have tools there but no nbmake there.)
>
> Then I did:
>
> ./build.sh -U -T /usr/obj/tooldir.NetBSD-3.99.24-i386 kernel=JCR20070405
>
> What is the purpose of figuring this out manually? Can't build.sh be
> smarter?
>
>
>  Jeremy C. Reed
>