From owner-freebsd-current Tue Apr 4 22:20:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA03567 for current-outgoing; Tue, 4 Apr 1995 22:20:12 -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 WAA03561 for ; Tue, 4 Apr 1995 22:20:11 -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 WAA21349 for ; Tue, 4 Apr 1995 22:17:16 -0700 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Wed, 5 Apr 1995 00:19:42 -0500 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 5 Apr 1995 00:19:45 -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 >Richard, is this an 'acceptable' solution? (I know it's not the best >solution, but we don't have that yet) Actually, I can live with either solution as a temporary measure. The recognition that it is "stopgap" rather than "correct" is the important feature to me. What I don't want to see is the propogation of a wrong philosophy. My whole point is that none of the code is written for a single static environment. We need to make sure that we are moving in the direction of environment based references. When you want to make a "tool" to use now, the execution environment is the HOST system. When you make that same tool to be included in a release, the execution environment is that of the TARGET. However, the source code for that tool is exactly the same. Only the libraries and, by extension, the include files that define their interface are changed. "Make"ing in these different environments will in general produce different results -- results that should end up in different places. ---- Richard Wackerbarth rkw@dataplex.net