From owner-freebsd-current Wed Feb 22 17:50:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA14136 for current-outgoing; Wed, 22 Feb 1995 17:50:25 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id RAA14121 for ; Wed, 22 Feb 1995 17:50:16 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id SAA16901 for current@FreeBSD.org; Wed, 22 Feb 1995 18:53:40 -0700 Date: Wed, 22 Feb 1995 18:53:40 -0700 From: Nate Williams Message-Id: <199502230153.SAA16901@trout.sri.MT.net> X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: current@FreeBSD.org Subject: Include files and 'release' engineering Sender: current-owner@FreeBSD.org Precedence: bulk I'm sure there is a way to have your cake and eat it too w/regards to the include files. Poul wants to be able do: 'cc -I$(DESTDIR)/usr/include -L$(DESTDIR) ....' and it will 'Do The Right Thing' Garrett and I want to be able to keep in sync with the kernel w/out daily runs of 'cd /usr/src/include; make all install'. The problem: Currently, the stuff install in /usr/include/{sys|net|...} use the symlink /usr/include sys -> /sys/sys, which still resolves to /sys/sys even when $(DESTDIR) is set. What we need is some Apollo-Domain hacking, but since we don't have that, what else can we do? Solution: When $(DESTDIR) is set completely populate $(DESTDIR)/usr/include as it is done now when COPIES != SHARED. Then, $(DESTDIR)/usr/include is completely valid, AND we can still allow shared /usr/include for the 'developers' case? The other problems with building the release with the tools in $(DESTDIR) are orthogonal to this, and are much more complicated than some people would like them to sound. What other problems exist with making the tree self-hosting? (not including the above two problems) Nate