From owner-freebsd-current Wed Feb 22 17:07:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id RAA13120 for current-outgoing; Wed, 22 Feb 1995 17:07:47 -0800 Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id RAA13114 for ; Wed, 22 Feb 1995 17:07:45 -0800 Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.9/8.6.9) with SMTP id TAA20791 for ; Wed, 22 Feb 1995 19:07:15 -0600 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 22 Feb 1995 19:07:17 -0600 To: current@freefall.cdrom.com From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: TRUE and FALSE Sender: current-owner@FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: >Hang on, you lost an important point here: Anything in the FreeBSD >source will reference the "internal includes", that is relative paths >to the include dirs. Only things like $HOME/hello.c will be at risk... I think that this is an important point. NOTHING in a system build should depend on the installed system on which it is running. If a user wants to compile code to run on her local machine, she should get /usr/include by default. But we MUST eliminate that from our code. There are three separate env's. The HOST which is running. The cross-compiler TOOLS which run on the HOST and generate TARGET code. The TARGET is the new kernel and all the programs that go with it. All packed up in distribution tarballs, etc. I should be able to compile the code for FreeBSD 2.1 on my MacII running MacBSD. And if it were not for the Makefile problems, I could do it under MPW. In general, we are working in the simple case HOST === TARGET, but that is not the general case for which we should be configured. ---- Richard Wackerbarth rkw@dataplex.net