From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 28 22:03:43 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 57C4B1065670; Mon, 28 Mar 2011 22:03:43 +0000 (UTC) Date: Mon, 28 Mar 2011 22:03:43 +0000 From: Alexander Best To: freebsd-hackers@freebsd.org Message-ID: <20110328220343.GA44745@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: src.conf(5) status/semantics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2011 22:03:43 -0000 hi there, how hard would it be to change the *.mk code so the following semantics apply: - make.conf(5) == applies system-wide - src.conf(5) == applies only to /usr/src right now certain settings will not be picked up from src.conf(5), like CC or CXX. it seems src.conf(5)'s puspose atm is limited to setting WITHOUT_* options. as can be noticed in several questions on current@, toolchain@ and questions@, the current behavior is non-intuitive. a lot of users don't understand why certain settings inside /etc/src.conf don't get picked up when building a target such as buildkernel or buildworld. expecially in connection with switching to clang and clang++ confusion has been noticable more than once. cheers. alex -- a13x