I've been running 2.0RC5 for a few weeks now on my SPARCstation 20 and
compiles have been running quite happily. When the release version got
tagged in CVS I duly checked it out and got started building myself a
distribution.

'./build.sh tools' ran quite happily although I was confused to see that it
produced '/usr/src/tooldir.NetBSD-2.0_RC5-sparc' even though I'd checked out
the 2.0 release branch from CVS. Anyways, I compiled an SMP kernel quite
happily using these tools and without implicitly specifying that tooldir (it
automatically used tooldir.NetBSD-2.0_RC5-sparc for the kernel build).

'uname -a' duly reports that I'm running a 2.0, as opposed to 2.0RC5,
kernel:

NetBSD wintermute 2.0 NetBSD 2.0 (WINTERMUTE.MP) #0: Wed Dec  1 15:28:11 GMT
2004  garyp@wintermute:/usr/obj/sys/arch/sparc/compile/WINTERMUTE.MP sparc

Now here's the fun part, I wanted to build a distribution to upgrade the
rest of the system with. './build.sh -j3 distribution' duly ran through it's
cleandir and obj sections but when it got to rebuilding nbmake it put it in
'/usr/src/tooldir.NetBSD-2.0-sparc' (note the lack of RC5 there). Things
proceeded quite happily until much later in the build when it started
looking for all manner of other binaries which obviously weren't there as
'./build.sh tools' put them in a different directory.

So, is this a bug in the build scripts or am I missing something obvious
like needing to specify where my tooldirs are built and where subsequent
uses of build.sh should look for them?

--
/-Gary Parker-----------------------f-Loughborough University-\
n IT Bandwidth Management Specialist - http://www.bmas.ja.net |
| Computing Services      - http://www.lboro.ac.uk/computing/ o
\r----------------------------------------------------------d-/