In article <20030429151229.L26297@snowdrop.l8s.co.uk> you write:
>> Thanks. That's working. Why aren't all include files in the NetBSD
>> tree used by default? Wouldn't that prevent problems like this when
>> not compiling on NetBSD?
>
>No, you have to use the build system's header files when running programs
>that run on the build system, otherwise you will get incorrect defines (etc).

... except of course where you're building parts of (e.g.) NetBSD's libc to
run on the host, where you need a mixture of host and NetBSD header files. 
The current build mechanism doesn't do this right, but it turns out to
mostly work.  It falls over when presented with a system which is similar
enough to NetBSD that internal header file names clash, but distinct enough
that using the wrong header file doesn't just work.  Hence, FreeBSD is
actually a really difficult host system.

I have the germ of an idea how to solve this properly, but it's quite a bit
trickier than it looks.

-- 
Ben Harris                                                   <bjh21@netbsd.org>
Portmaster, NetBSD/acorn26           <URL:http://www.netbsd.org/Ports/acorn26/>