>I'm attempting to set up automated nightly builds of -current.. from a
>cross-compiling environment. My initial target is to build -current on a 1.4.2
>host.

First off: hurray! This is important work for slow arches and for new ports.

Now: how does your cross-compiler find its headers? If it takes _anything_
from /usr/include then it's going to have problems. We should be compiling
with "-nostdinc -I$(BSDSRCDIR)/xinclude" and have 'make includes' install
into $(BSDSRCDIR)/xinclude. $(DESTDIR)/usr/include should get updated at
'make install' time, not 'make includes' time.

(I would have preferred $(BSDSRCDIR)/include, but that's already taken.)

I believe that when a kernel is updated, no headers should need to change
(those that do probably shouldn't have been made visible to userland in the
first place). Building and installing libc & friends will install the new
interfaces along with the binaries that export them.

Most likely we have some gnarly header dependencies in the current system
that won't be handled well by this model. I have faith that they can be
reorganized without unacceptable pain.

Todd Whitesel
toddpw @ best.com