From owner-freebsd-current@FreeBSD.ORG Wed Sep 7 17:20:09 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 4234A106564A; Wed, 7 Sep 2011 17:20:09 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 065F88FC0A; Wed, 7 Sep 2011 17:20:09 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:14f9:cfdf:caf2:2c18]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 58D314AC31; Wed, 7 Sep 2011 21:20:07 +0400 (MSD) Date: Wed, 7 Sep 2011 21:20:04 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1997790603.20110907212004@serebryakov.spb.ru> To: Dimitry Andric In-Reply-To: <4E67A720.2000903@FreeBSD.org> References: <1231707981.20110907201053@serebryakov.spb.ru> <4E67A720.2000903@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: lev@FreeBSD.org, 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 Reply-To: lev@FreeBSD.org 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:20:09 -0000 Hello, Dimitry. You wrote 7 =F1=E5=ED=F2=FF=E1=F0=FF 2011 =E3., 21:17:20: >> 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 IMHO, it is bug in build process ;-) -- see below > 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 I think, that /usr/bin/cpp is valuable by itself, as it is handy generic preprocessor tool, useful for preparing complex ipfw scripts, for example. All others are bundled together, for sure. I think, it is good idea to exclude cpp from this list (but not from WITHOUT_TOOLCHAIN, of course). --=20 // Black Lion AKA Lev Serebryakov