From owner-freebsd-current Tue Jan 5 16:00:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05903 for freebsd-current-outgoing; Tue, 5 Jan 1999 15:58:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA05898 for ; Tue, 5 Jan 1999 15:58:46 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: current@freebsd.org Subject: building boot From: "Robert V. Baron" Date: 05 Jan 1999 18:57:41 -0500 Message-ID: Lines: 10 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG 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