From owner-freebsd-hackers  Mon Oct 18 12:21:55 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 583)
	id E0C7614F82; Mon, 18 Oct 1999 12:21:53 -0700 (PDT)
To: dcs@newsguy.com, marcel@scc.nl
Subject: Re: kernel/loader & world
Cc: bde@freebsd.org, hackers@freebsd.org, mike@smith.net.au,
	peter@freebsd.org
In-Reply-To: <380B60D4.145054C0@scc.nl>
Message-Id: <19991018192153.E0C7614F82@hub.freebsd.org>
Date: Mon, 18 Oct 1999 12:21:53 -0700 (PDT)
From: bde@FreeBSD.ORG (Bruce Evans)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > 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 <machine/*>, 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.

The bug is that the `machine' symlink is not always created.  The
makefile supports creating it, but has missing dependencies.  See
the old boot loader (sys/i386/boot/Makefile.inc) for a good way to
handle this.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message