From owner-freebsd-current Tue Jan 5 16:10:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09108 for freebsd-current-outgoing; Tue, 5 Jan 1999 16:10:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09099 for ; Tue, 5 Jan 1999 16:10:54 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA04059; Tue, 5 Jan 1999 16:07:39 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdEE4053; Wed Jan 6 00:07:33 1999 Date: Tue, 5 Jan 1999 16:07:30 -0800 (PST) From: Julian Elischer To: "Robert V. Baron" cc: current@FreeBSD.ORG Subject: Re: building boot In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you may need to do "make includes" in /usr/src On 5 Jan 1999, Robert V. Baron wrote: > > I recently pulled down a new src/sys and tried to build boot. This > did not work too well, because the app environment and includes files > were a month old. Basically, the machine/ansi.h was missing the __int > typedefs. So should boot/ be treated like the kernel and just use > kernel relative headers or should it be like any old user program and > just depend on /usr/include. Currently boot/ does both. It can > pull in things from sys/sys relative to the the kernel src. But > it also tries to get things relative to machine -- which is not > otherwise defined so it pulls from /usr/include/machine. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message