On 10/08 01:31, Daniel Bolgheroni wrote:
> But, even with the new source tree, when I build the toolchain, I get I'm 
> using the older version of source tree, 1.6U.
> 
> Look at it (using up-to-date source tree):
> 
> (...)
> 
> ===> Summary of results:
>          build.sh command: ./build.sh tools
>          build.sh started: Tue Oct  7 23:53:40 UTC 2003
>          Bootstrapping nbmake
>          MACHINE:          i386
>          MACHINE_ARCH:     i386
>          TOOLDIR path:     /usr/src/tooldir.NetBSD-1.6U-i386
>          DESTDIR path:     /usr/src/destdir.i386
>          RELEASEDIR path:  /usr/src/releasedir
>          Created /usr/src/tooldir.NetBSD-1.6U-i386/bin/nbmake
>          makewrapper:      /usr/src/tooldir.NetBSD-1.6U-i386/bin/nbmake-i386
>          Updated /usr/src/tooldir.NetBSD-1.6U-i386/bin/nbmake-i386
>          Tools built to /usr/src/tooldir.NetBSD-1.6U-i386
>          build.sh started: Tue Oct  7 23:53:40 UTC 2003
>          build.sh ended:   Wed Oct  8 00:02:21 UTC 2003
> ===> .

That's normal. The 1.6U that you see there is from uname(1) on the host
system, which, as you say, is running 1.6U. If you were to build.sh
kernel=GENERIC, copy the new kernel into place, reboot, and build.sh
tools you would see 1.6ZC there instead of 1.6U. It's just a pathname.
It isn't important.

If you want to see what kernel version will be generated by your source
tree (not very useful, really, as much can change during the lifetime of
that version), look in sys/conf/osrelease.sh.