From owner-freebsd-current  Sun Nov 12 15:44:48 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA13457
          for current-outgoing; Sun, 12 Nov 1995 15:44:48 -0800
Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA13410
          ; Sun, 12 Nov 1995 15:44:32 -0800
Received: (from mark@localhost) by linus.demon.co.uk (8.7.1/8.7.1) id XAA00478; Sun, 12 Nov 1995 23:04:39 GMT
Date: Sun, 12 Nov 1995 23:04:39 GMT
From: Mark Valentine <mark@linus.demon.co.uk>
Message-Id: <199511122304.XAA00478@linus.demon.co.uk>
In-Reply-To: Richard Wackerbarth's message of Nov 11,  4:34pm
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: rkw@dataplex.net (Richard Wackerbarth), Terry Lambert <terry@lambert.org>
Subject: Re: LKM's still wont compile in -current
Cc: current@freebsd.org, root@deadline.snafu.de, hackers@freebsd.org
Sender: owner-current@freebsd.org
Precedence: bulk

> From: rkw@dataplex.net (Richard Wackerbarth)
> Date: Sat 11 Nov, 1995
> Subject: Re: LKM's still wont compile in -current

> Now can I sell "you" (the holdouts, not you Terry) on getting rid of the
> absolute paths?
> EVERYTHING needs to be referenced relative to the ROOT of the build tree.
> SRC, OBJ location, TOOLS, INCludes, MKfiles, etc. EVERYTHING.

I'd draw a line below EVERYTHING, at least for initial bootstrapping.

I'd separate out some of the tools, like the compiler and make, just
documenting which versions you need to have installed in the host environment
to build for your target (point src/make.conf at them if they're not in the
standard locations).  If you need to, you build the tools you need as part of
bootstrapping your build environment.

Some stuff, like config, will always be used from the build tree, though.

		Mark.