Subject: Re: Toolchain build fails for 1.6
To: Matthew Kolb , Paul Frommeyer <paul@palas.com>
From: Allen Briggs <briggs@wasabisystems.com>
List: port-macppc
Date: 06/29/2004 21:27:23
On Tue, Jun 29, 2004 at 06:24:11PM -0500, James Chacon wrote:
> > Here's the deal.  You wouldn't need to do a toolchain build if you 
> > didn't get new src.  You could simply use the make, cc, and config on 
> > your currently running system (just as you said you could do with other 
> > OSs).
> 
> Not always guarenteed. If you were on 1.6 and wanted to come up to -current
> you needs new tools. Compiler has changed, config has updates, etc.

Just to pick a nit, I think you're actually in agreement.  If you have
the source for the version of the OS that you already have installed and
running, you don't need to build new tools.  If you're building newer
(or older) sources, then you probably do want/need to do the full build
w/ new tools and all.  Essentially, you're cross-building one OS (newer
NetBSD) on another (older NetBSD).  This process has much improved life
on the edge (tracking -current)...

> In general on the release branch you're safe, but otherwise don't assume this.

Reasonable advice, but even there, it's possible that you want to build
tools for an upgrade.  There may have been, for example, bugfixes to the
toolchain...  But that's reaching a little for an example and falls
outside your "In general" qualification...

-allen

-- 
 Allen Briggs                     briggs@wasabisystems.com
 Wasabi Systems, Inc.             http://www.wasabisystems.com/