From owner-freebsd-current@FreeBSD.ORG Thu Apr 20 15:54:41 2006 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B6CA16A401; Thu, 20 Apr 2006 15:54:41 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DC1843D45; Thu, 20 Apr 2006 15:54:40 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp5-g19.free.fr (Postfix) with ESMTP id 480582768F; Thu, 20 Apr 2006 17:54:39 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 416309BD9F; Thu, 20 Apr 2006 15:54:38 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 21C74405B; Thu, 20 Apr 2006 17:54:38 +0200 (CEST) Date: Thu, 20 Apr 2006 17:54:38 +0200 From: Jeremie Le Hen To: Ruslan Ermilov Message-ID: <20060420155438.GC68951@obiwan.tataz.chchile.org> References: <20060317165638.GA1172@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060317165638.GA1172@ip.net.ua> User-Agent: Mutt/1.5.11 Cc: current@FreeBSD.org Subject: Re: [fbsd] [HEADS UP] New world/kernel build options are imminent X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 15:54:41 -0000 Hi, Ruslan, > Basically, the new implementation looks like this: > > - There are MK_* options that are set either to "no" or "yes". > Makefiles test them with either ``== "no"'' or ``!= "no"''. > Users have no direct control over these variables, and attempt > to set them will result in an error from make(1). Most options > default to "yes", but some default to "no". Options may have > dependencies. > > - Then there are WITH_*/WITHOUT_* user configurable knobs (value > is not important). WITH_FOO changes MK_FOO to "yes", WITHOUT_FOO > changes MK_FOO to "no". Both WITH_FOO and WITHOUT_FOO can't be > set at the same time, attempt to do so will result in an error. During the early buildworld process, I need to disable a feature that may have been enabled in src.conf(5) with the WITH_FOO knob. IOW, I want to be sure that the feature FOO is disabled for legacy, bootstrap-tools, build-tools and cross-tools targets. However if the WITH_FOO knob is enabled in src.conf(5), using "WITHOUT_FOO=" inside BMAKE, TMAKE and XMAKE macros would lead to an error triggered by bsd.own.mk : % 373 .if defined(WITH_${var}) && defined(WITHOUT_${var}) % 374 .error WITH_${var} and WITHOUT_${var} can't both be set. % 375 .endif How should I handle that ? I could override SRCCONF and set it to /dev/null, but I don't think it is acceptable because according to Makefile.inc1, bootstrap-tools, build-tools and cross-tools targets might be influenced by src.conf(5) knobs. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >