On Wed, 8 Oct 2003, Daniel Bolgheroni wrote:
> On Wednesday 08 October 2003 03:59, Frederick Bruckman wrote:
> > On Wed, 8 Oct 2003, Daniel Bolgheroni wrote:
> > > I've updated my source tree recently and compiled a new toolchain to
> > > compile a new kernel.
> > >
> > > I was using 1.6U (don't remenber the date), but even after the update,
> > > the version I'm getting is the same. I saw that NetBSD -current is at
> > > 1.6ZC or something like that.
> >
> > Exactly what is the wrong version? "uname -v" is how you tell what
> > version of the kernel you are booted from.
>
> I've downloaded -current from anoncvs few months ago, when the version was
> labeled 1.6U. I'm still using this version.
>
> But, these days, I've updated my source tree and the -current from these days
> are not labeled 1.6U anymore. It got a new label, like 1.6ZC or something
> like that (take a look at the letters after the number).
>
> 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
> ===> .
The version you see there is the version of the build host (which is
still 1.6U). Once you build and boot the new kernel, or boot a generic
kernel out of the newly built release, "uname -v" will show the new
version. The next build, by default, will create a tooldir with
NetBSD-1.6ZC in the name.
The tools are built by and for a particular host, which only happens
to be the host you intend to upgrade -- you can build
NetBSD-1.6.1_STABLE on NetBSD-1.6ZC, and vice-versa, and so on, but
you can't necessarily run native binaries built for on on the other.
Frederick