Subject: Re: Toolchain Update (27-Nov-2001)
To: Frederick Bruckman <>
From: Todd Vierling <>
List: tech-toolchain
Date: 11/28/2001 16:08:43
On Wed, 28 Nov 2001, Frederick Bruckman wrote:

: > : These Makefiles have no clue that they're running as part of a pkgsrc
: > : build, and as such, if pkgsrc is located inside /usr/src, end up
: > : catching all the tools framework.
: >
: > I've added something to (rev. 1.65) that sets USETOOLS=no --
: > both for bsd.pkg*.mk and via MAKE_ENV for invoked builds.  This should allow
: > pkgsrc to be located inside "src" without trouble.
: What happens if I try to build one of these packages out-of-the-box,
: without pkgsrc?

So log as you:

* don't set USETOOLS=yes explicitly in mk.conf

* don't put the source tree of this third party package under NetBSD's
  `src' tree

you'll use the installed compiler.  The default for USETOOLS is `no' outside
of the tree or when building kerbels, and `yes' when building inside a
complete `src' tree.  This magic is in <>.

: > Now, why DESTDIR was being picked up for gr is unrelated to this, as his
: > pkgsrc was located outside of src.  It's probably the BSD Makefile issue you
: > described above.
: It shouldn't hurt anything to add BSD_PKG_MK to ${MAKE_ENV}, if that's
: what's required.

Right, but as I said, I don't know whether this would harm people too.  It's
my gut feeling that it'd be better to turn off everything guarded by
BSD_PKG_MK in mk.conf, but I wonder if that might exclude some compile
options that the builder may actually want.

-- Todd Vierling <>  *  Wasabi & NetBSD:  Run with it.
-- CDs, Integration, Embedding, Support --