From owner-cvs-all Fri Jun 7 20:16: 0 2002 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EAD9D37B407; Fri, 7 Jun 2002 20:15:50 -0700 (PDT) Received: (from matusita@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g583FoW57495; Fri, 7 Jun 2002 20:15:50 -0700 (PDT) (envelope-from matusita) Message-Id: <200206080315.g583FoW57495@freefall.freebsd.org> From: Makoto Matsushita Date: Fri, 7 Jun 2002 20:15:50 -0700 (PDT) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/release Makefile X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG matusita 2002/06/07 20:15:50 PDT Modified files: release Makefile Log: Explicitly set TARGET and TARGET_ARCH in a chroot sandbox. In fact, these variable are set as environment variables since we run "make TARGET=xxx TARGET_ARCH=xxx"; TARGET and TARGET_ARCH are declared in the command line arguments. However, if you are not make(1) guy, it is hard to understand that TARGET/TARGET_ARCH are appropriately set in a chroot environment (as environment variables). Now, the only environment variable need to be set explicitly is 'PATH'. If we set PATH in /mk script, we can make pristine sandbox for release build (i.e., "env -i /usr/sbin/chroot ${CHROOT} /mk" will work). Valuable comments about this issue from: ru Tested on (virtually): snapshots.jp.FreeBSD.org MFC after: 2 weeks Revision Changes Path 1.686 +7 -1 src/release/Makefile To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message