From owner-freebsd-hackers Mon Oct 18 11: 3:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id CBB1815168; Mon, 18 Oct 1999 11:03:07 -0700 (PDT) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11dH8h-000Bkk-00; Mon, 18 Oct 1999 18:04:07 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id UAA51080; Mon, 18 Oct 1999 20:03:00 +0200 (CEST) (envelope-from marcel@scc.nl) Message-ID: <380B60D4.145054C0@scc.nl> Date: Mon, 18 Oct 1999 20:03:00 +0200 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel C. Sobral" Cc: hackers@freebsd.org, Mike Smith , peter@freebsd.org, bde@freebsd.org Subject: Re: kernel/loader & world References: <380B50CB.AA3808E1@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > Well, once I discarded my preconceptions and re-read the error > message, the problem is obvious: > > In file included from > /usr/src/sys/boot/i386/libi386/../../../sys/signal.h:236, > from > /usr/src/sys/boot/i386/libi386/../../../sys/param.h:90, > from > /usr/src/sys/boot/i386/libi386/aout_freebsd.c:29: > /usr/src/sys/boot/i386/libi386/../../../sys/ucontext.h:34: > machine/ucontext.h: No such file or directory > > We include the files directly from the source tree, but some of them > then go and include files from , which, of course, refers > to /usr/include/machine/*. Thus, some of the files are up-to-date, > and some are not. Unless you build world first. It's dangerous to mix headers from the source tree with headers from /usr/include. Are you sure this is the case? > [but you can't build world until you booted a new kernel, and you > can't boot a new kernel until you have a new loader, but you can't > build a new loader...] This is "artifical" in that it is solved by fixing the build process. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message