Subject: Re: Problem in new toolchain builds (need comments)
To: James Chacon <firstname.lastname@example.org>
From: Todd Vierling <email@example.com>
Date: 10/23/2001 19:47:26
On Tue, 23 Oct 2001, James Chacon wrote:
: When USETOOLS's gets set in bsd.own.mk (basically via USE_NEW_TOOLCHAIN right
: now but eventually as the default on all platforms) it overrides all the
: toolchain vars to reference the ones in $TOOLDIR.
: It specifically doesn't set TOOLDIR if BSD_PKG_MK is set. However, that doesn't
: What about source that uses the system .mk files (say bsd.prog.mk) to build
I was thinki9ng about just this issue yesterday, and there is a simpler
solution than even what you provided. Since USETOOLS=yes is intended to be
used with top-level builds, and USETOOLS=no with one-off or partial tree
builds, it's actually rather easy to default it to "no" in bsd.own.mk and
set it, with MAKEFLAGS propagation, in src/Makefile.
I'll make the appropriate change and document it in the toolchain design doc
that will be checked in this evening.
-- Todd Vierling <firstname.lastname@example.org> * Wasabi NetBSD: Run with it.
-- CDs, Integration, Embedding, Support -- http://www.wasabisystems.com/