which "include" being used?

[Garrett Cooper]

On Sep 20, 2011, at 6:19 PM, Kevin Oberman <kob6558 at gmail.com> wrote:

> On Sep 20, 2011 6:09 PM, "paradox" <ddkprog at yahoo.com> wrote:
>> 
>> try remove or move /usr/include
>> and rebuild the world
>> 
>>> wrote:
>>>> Why build the world uses /usr/include ?
>>>> why not use "include" from the /obj/...include ?
>>>> 
>>>> issue to "build world" with loss of multiple files at
>>> /usr/include/
>>> 
>>> Did your make "build world" or "buildworld"? It should be
>>> all one word
>>> and it does use
>>> the header files in /usr/obj/... or /usr/src/... At least
>>> for me, it
>>> does. Failing to do so
>>> would break a lot of things.
>>> 
>>> You should also look at the magic done by the .mk files.
>>> This does
>>> make some of the
>>> header files look like they were pulled from /usr/includes
>>> because of
>>> the things the .mk
>>> files do to your environment.
> 
> Sorry. I misunderstood.
> 
> To build a new system, you have to start with something. You build the
> toolcain  and gcc. Those have to be built first with the existing compiler
> and toolchain which uses the existing system include files.
> 
> Later in buildworld, they are re-built using the new toolchain, compiler,
> and header files.
> 
> If you lost your system header files, you will need to restore them before
> you can re-build the system.
> Sorry.

I'd unpack a tarball from the most recent release. It's the easiest way to fix things :)..
-Garrett