From owner-freebsd-current@FreeBSD.ORG Wed Sep 7 17:17:22 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDA6C106566B; Wed, 7 Sep 2011 17:17:22 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9068C8FC14; Wed, 7 Sep 2011 17:17:22 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:c014:d233:d8d3:2f47] (unknown [IPv6:2001:7b8:3a7:0:c014:d233:d8d3:2f47]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 6FC185C59; Wed, 7 Sep 2011 19:17:21 +0200 (CEST) Message-ID: <4E67A720.2000903@FreeBSD.org> Date: Wed, 07 Sep 2011 19:17:20 +0200 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.1) Gecko/20110830 Thunderbird/6.0.1 MIME-Version: 1.0 To: lev@FreeBSD.org References: <1231707981.20110907201053@serebryakov.spb.ru> In-Reply-To: <1231707981.20110907201053@serebryakov.spb.ru> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current Subject: Re: WITHOUT_GCC flag disables installation of /usr/bin/cpp too -- is it Ok? 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: Wed, 07 Sep 2011 17:17:22 -0000 On 2011-09-07 18:10, Lev Serebryakov wrote: > I'm building NanoBSD image based on latest HEAD sources. I've added > WITHOUT_GCC to install configuration, as I don't need gcc/g++ (it is > documented in man src.conf as disabling exactly gcc and g++), but it > affect /usr/bin/cpp too. And I need cpp for some config processing. > > Is it bug in documentation (man src.conf) or build system? I know > about WITHOUT_TOOLCHAIN, and it seems reasonable, that > WITHOUT_TOOLCHAIN disables cpp too, but not WITHOUT_GCC :(. It's a bug in the documentation. WITHOUT_GCC actually disables at least the following executables: /usr/bin/c++ /usr/bin/c++filt /usr/bin/CC /usr/bin/cc /usr/bin/cpp /usr/bin/g++ /usr/bin/gcc /usr/bin/gcov /usr/libexec/cc1 /usr/libexec/cc1plus