From owner-freebsd-current@FreeBSD.ORG Wed Sep 21 00:14:55 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 161F9106566C for ; Wed, 21 Sep 2011 00:14:55 +0000 (UTC) (envelope-from freebsd-current-local@be-well.ilk.org) Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.42]) by mx1.freebsd.org (Postfix) with ESMTP id E284D8FC19 for ; Wed, 21 Sep 2011 00:14:54 +0000 (UTC) Received: (qmail 2999 invoked from network); 20 Sep 2011 23:45:16 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Sep 2011 23:45:15 -0000 Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.8]) by be-well.ilk.org (Postfix) with ESMTP id 2139D2E0CE; Tue, 20 Sep 2011 19:45:09 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id CF8DD39830; Tue, 20 Sep 2011 19:45:08 -0400 (EDT) From: Lowell Gilbert To: paradox References: <1316542838.11969.YahooMailClassic@web120526.mail.ne1.yahoo.com> Date: Tue, 20 Sep 2011 19:45:08 -0400 In-Reply-To: <1316542838.11969.YahooMailClassic@web120526.mail.ne1.yahoo.com> (paradox's message of "Tue, 20 Sep 2011 11:20:38 -0700 (PDT)") Message-ID: <447h52ye0r.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-current@freebsd.org Subject: Re: which "include" being used? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@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, 21 Sep 2011 00:14:55 -0000 paradox writes: > Why build the world uses /usr/include ? > why not use "include" from the /obj/...include ? First it builds the toolchain, including the include files (as well as the compiler, etc.). To do this, it has to use the system include files. Once that is done, it uses the newly built tools and not the system ones. > issue to "build world" with loss of multiple files at /usr/include/ You'll need to restore them some other way to be able to run buildworld. Assuming you build and install the world successfully, you will then have a correct set of files in /usr/include.