Subject: Re: WARNING: -current toplevel build process changing!
To: None <>
From: Lars-Johan Liman <>
List: tech-toolchain
Date: 06/03/2001 08:46:16
On Fri, 1 Jun 2001, Bernd Ernesti wrote:
> : Why NOT /etc/mk.conf?
> Because the top level make needs to work on *vendor* makes, which may not be
> bmake, and thus cannot read /etc/mk.conf.  The bootstrap harness builds
> bmake from the source tree in use, and needs to put it in TOOLDIR, which has
> to be defined *BEFORE* bmake is run.

> Now, I can probably put in some kind of hook to try to pry this out of
> mk.conf if the native system make is bmake.  I'll look into this.

Err... doesn't NetBSD-make look in both the environment and
/etc/mk.conf? If so, Bernd's question still holds. If you happen do be
running on a NetBSD system you should be free to set variables like
that in mk.conf, if not (= you use a vendor-make) you can set them in
the environment instead.

If not NetBSD-make _doesn't_ check both mk.conf and ENV, then why
doesn't it?

# Lars-Johan Liman		! E-mail:
# Senior Systems Specialist     ! HTTP  : //
# Autonomica AB, Stockholm 	! Voice : +46 8 - 615 85 72