From owner-cvs-src@FreeBSD.ORG Wed Oct 12 18:07:56 2005 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9011816A41F; Wed, 12 Oct 2005 18:07:56 +0000 (GMT) (envelope-from gad@FreeBSD.org) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75E2243D66; Wed, 12 Oct 2005 18:07:53 +0000 (GMT) (envelope-from gad@FreeBSD.org) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j9CI7poq001524; Wed, 12 Oct 2005 14:07:52 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <20051012170509.GH99170@submonkey.net> References: <200510121009.j9CA9aE3026075@repoman.freebsd.org> <20051012.091330.53066886.imp@bsdimp.com> <20051012152710.GC75270@ip.net.ua> <20051012.104300.74694006.imp@bsdimp.com> <20051012170509.GH99170@submonkey.net> Date: Wed, 12 Oct 2005 14:07:50 -0400 To: ru@FreeBSD.org, yar@FreeBSD.org From: Garance A Drosehn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.1 Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/make make.1 X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2005 18:07:56 -0000 At 6:05 PM +0100 10/12/05, Ceri Davies wrote: >On Wed, Oct 12, 2005, Warner Losh wrote: > > From: Ruslan Ermilov > > > > > > __MAKE_CONF doesn't fall under "make sets or knows about the > > > following internal variables or environment variables". Seems to me that it does. I think the detailed description could remain in make.conf(5), but that the variable name should still be explicitly mentioned in make(1). > > > Rather, it's a FreeBSD specific feature, it doesn't have > > > any direct connection to the make utility (as well as > > > CPUTYPE, CFLAGS, etc.). The man page documents the make utility on FreeBSD. The fact that __MAKE_CONF is a FreeBSD-specific feature does not change the fact that setting __MAKE_CONF will effect *every* invocation of 'make'. It is *not* limited to makefiles in /usr/src and /usr/ports. So, the following comment in make.conf(5) is not completely accurate: The purpose of make.conf is not to [...]. Instead, it is included by the various makefiles in /usr/src, /usr/ports and /usr/doc which conditionalize their internal actions according to the settings found there. I just created a makefile in /tmp with nothing but the lines: all : echo "${CC} ${CFLAGS}" and when I type 'make all' in /tmp, the /etc/make.conf file is included. If I set __MAKE_CONF, and if that file changes the value of CC, then my 'make all' is changed. That /tmp/makefile does not explicitly .include any other file. The effect of __MAKE_CONF is not limited to FreeBSD-project makefiles. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA