From owner-freebsd-current Tue Apr 4 12:28:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA20933 for current-outgoing; Tue, 4 Apr 1995 12:28:37 -0700 Received: from mail.barrnet.net (mail.BARRNET.NET [131.119.246.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA20927 for ; Tue, 4 Apr 1995 12:28:32 -0700 Received: from dataplex.net (SHARK.DATAPLEX.NET [199.183.109.241]) by mail.barrnet.net (8.6.10/MAIL-RELAY-LEN) with ESMTP id MAA17798 for ; Tue, 4 Apr 1995 12:25:37 -0700 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Tue, 4 Apr 1995 14:28:04 -0500 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 4 Apr 1995 14:28:06 -0500 To: Nate Williams From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: cvs commit: src/sys/i386/conf Makefile.i386 Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >*BLECH* BSD systems have *never* (and should *never*) require that you >have the complete source tree installed just to build a kernel. Making >them go through alot of trouble to build a kernel is a waste of their >time. Many, many more people build kernels w/out src trees than people >who build kernels w/src trees. We are trying to make the system >*easier* to use for the avg. user w/out penalizing the developer. > >Show me a solution that does that and it'll get into the tree. If it >doesn't provide both, then it's not a complete solution. I wanted to >provide a ENVIRONMENT variable which was set to provide /usr/src/include >protection, but it was show down. But I totally support the ENVIRONMENT variable. That is THE ONLY WAY you can have your cake and .... For those who want the "simple" approach, the defaults can pick up /usr/include. Actually, the general case is a more complex. You are doing two different things and they each need to be self contained. 1) You are building "tools" with which you will later build a system, and 2) You are building a system that will then be installed (on another machine) In case 1) the includes are those appropriate for the current system/libraries, and in case 2) the includes belong to the target system. In general, they are NOT the same. ---- Richard Wackerbarth rkw@dataplex.net