From owner-freebsd-current Wed Jul 12 11:25:53 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA14204 for current-outgoing; Wed, 12 Jul 1995 11:25:53 -0700 Received: from dataplex.net (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA14198 for ; Wed, 12 Jul 1995 11:25:51 -0700 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Wed, 12 Jul 1995 12:49:37 -0500 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 12 Jul 1995 12:49:37 -0500 To: Bruce Evans From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Help me please.. :) Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk Bruce Evans writes: >There are hundreds of bugs here :-). We need to support multiple >machines someday. Then files in /usr/include/machine can't work even if >it is a symlink. A symlink is still better because it can be changed >much faster. I agree there are MANY bugs. However, the "bug" is that any code relies on /usr/include/..., per se, at all. /usr/include should be used ONLY for applications to be run on THIS machine and under THIS version of the operating system. In general, the path to the appropriate include files needs to be a parameter of the Makefiles with the default becoming "/usr/include/" for applications. If someone is compiling a new version of the operating system, they should be required to specify the appropriate include environment for that configuration. ---- Richard Wackerbarth rkw@dataplex.net