From owner-freebsd-current  Tue Jun  9 22:02:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA22107
          for freebsd-current-outgoing; Tue, 9 Jun 1998 22:02:33 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22102
          for <freebsd-current@FreeBSD.ORG>; Tue, 9 Jun 1998 22:02:30 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA21808;
	Wed, 10 Jun 1998 15:02:26 +1000
Date: Wed, 10 Jun 1998 15:02:26 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199806100502.PAA21808@godzilla.zeta.org.au>
To: bde@zeta.org.au, jb@cimlogic.com.au
Subject: Re: Can't "make buildworld"
Cc: freebsd-current@FreeBSD.ORG, wpub1@triton.net
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> Does the -I override for making make break something?  I guess it does
>> if sys.mk is suitably old.
>
>The top level makefile (I think) always uses the included .mk files from
>/usr/share/mk which are not necessarily what is required to build the
>source on a non-up-to-date system. I'd say that the "official best

The top level is supposed to do very little, so that the files in
/usr/share/mk are good enough.  The point I'm concerned about is that
when -I is used to force use of src/share/*.mk for building `make',
it may give a conflicting set of .mk files - sys.mk from /usr/share/mk
and everything else source-relative.  At least one other bug has crept
in: the source-relative files are not used at all for bootstrapping
mtree.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message