Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Oct 1999 20:03:00 +0200
From:      Marcel Moolenaar <marcel@scc.nl>
To:        "Daniel C. Sobral" <dcs@newsguy.com>
Cc:        hackers@freebsd.org, Mike Smith <mike@smith.net.au>, peter@freebsd.org, bde@freebsd.org
Subject:   Re: kernel/loader & world
Message-ID:  <380B60D4.145054C0@scc.nl>
References:  <380B50CB.AA3808E1@newsguy.com>

next in thread | previous in thread | raw e-mail | index | archive | help
"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 <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.

-- 
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?380B60D4.145054C0>