From owner-freebsd-commit Tue Apr 4 01:02:24 1995 Return-Path: commit-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA06323 for commit-outgoing; Tue, 4 Apr 1995 01:02:24 -0700 Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA06308 for cvs-sys-outgoing; Tue, 4 Apr 1995 01:02:08 -0700 Received: from mpp.com (dialup-3-171.gw.umn.edu [134.84.101.171]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA06298; Tue, 4 Apr 1995 01:01:46 -0700 Received: (from mpp@localhost) by mpp.com (8.6.11/8.6.9) id CAA07819; Tue, 4 Apr 1995 02:19:04 -0500 From: Mike Pritchard Message-Id: <199504040719.CAA07819@mpp.com> Subject: Re: cvs commit: src/sys/i386/conf Makefile.i386 To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 4 Apr 1995 02:19:04 -0500 (CDT) Cc: nate@freefall.cdrom.com, CVS-commiters@freefall.cdrom.com, cvs-sys@freefall.cdrom.com In-Reply-To: <199504030240.TAA03137@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 2, 95 07:40:02 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1707 Sender: commit-owner@FreeBSD.org Precedence: bulk > > nate 95/04/02 18:13:51 > > > > Modified: sys/i386/conf Makefile.i386 > > Log: > > Added -I/usrinclude to the tail end of the INCLUDES line. This hack > > will cause kernel compiles to work even if the src/includes directory > > doesn't exist but still do the 'Right Thing' and pull files from the > > source tree if it does exist. > > > > Reviewed by: Bruce Evans > > Humm.. now what happens when these unknowing fools update there > /usr/src/sys tree and don't update /usr/include to match. They are > going to get kernel compiles that fall over, and we are going to > get bug reports about strange things happening :-(. > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com My feelings are that you should be able to build anything in /usr/src without /usr/include even being present on the machine you are running the build on. A good example might be that you have a development machine where you keep all of your sources, say a 2.0 source tree for your production machines, and a -current source tree for a development machine or two. If anything in the sources depends on /usr/include, one of those source trees isn't going to be happy. Now, just for the record, there are many things on the source tree that require that /usr/include contain the right version when doing a "make all" in /usr/src. This past weekend I was doing a make all, and there were a few files in libc that wouldn't compile until I installed the current include files into /usr/include. The previous time I did a make all I had the same problem. -- Mike Pritchard pritc003@maroon.tc.umn.edu "Go that way. Really fast. If something gets in your way, turn"