From owner-freebsd-current Thu Sep 18 22:19:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA11985 for current-outgoing; Thu, 18 Sep 1997 22:19:30 -0700 (PDT) Received: from usr05.primenet.com (tlambert@usr05.primenet.com [206.165.6.205]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA11980 for ; Thu, 18 Sep 1997 22:19:28 -0700 (PDT) Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id WAA11463; Thu, 18 Sep 1997 22:19:00 -0700 (MST) From: Terry Lambert Message-Id: <199709190519.WAA11463@usr05.primenet.com> Subject: Re: Yet Another bug in src/Makefile To: gurney_j@resnet.uoregon.edu Date: Fri, 19 Sep 1997 05:19:00 +0000 (GMT) Cc: dima@tejblum.dnttm.rssi.ru, freebsd-current@FreeBSD.ORG In-Reply-To: <19970918213446.00164@hydrogen.nike.efn.org> from "John-Mark Gurney" at Sep 18, 97 09:34:46 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > 'make -DCLOBBER world' will not remove /usr/include. It will remove > > /usr/obj/usr/src/tmp/usr/include instead... > > why should it remove /usr/include?? /usr/include is not used for the > building of the resulting binaries install.. why not do a rm -rf / > if you want to clean out the area your installing to... :) This is false. The build for libkvm references outside the source tree (specifically, an absolute reference via -I). This was why I hacked the symbolic links for multiple kernel tree builds (earlier posting). There are other builds which also reference out of the build tree; anything which references or , in particular, references /usr/include. A reference to can't be resolved without /usr/include/ since it refers to the postinstalled headers from /usr/src/sys/i386/include/ into /usr/include/machine/. The , , <*fs/*>, , and references are all in this boat, as well as others from package/base installation (, etc.), if installed. > of course there is good argument that the installed to area should > be clean to prevent old files from contaminating a setup... but > if we start to clean out /usr/include, we should also do /{bin,sbin} > /usr/{bin,share,sbin,lib,libexec} and any others that get installed... The argument is that the installed area should never be used for system build, since you may be building a cross-environment. You either need to build the machine link as part of the build, or you need variant symlinks (whole other kettle of fish) to deal with the architecture variant headers for cross-builds. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.