None of this explains why it is that I must install the includes into the
running system (ie /usr/include) before I can build (I encountered the same
problem as Darren with sys/endian.h, and doing "make includes" did not
solve it - I have DESTDIR set, and apparently the compilations aren't
looking in $DESTDIR/usr/include, only in /usr/include.) This makes DESTDIR
much less useful.

At 05:56 PM 9/5/99 +1000, Simon Burge wrote:
>Darren Reed wrote:
>
>> What I expected to find, when building a release, was to be able to build
>> it just like any other application - that is prior to installation, it
>> doesn't disturb the running setup in any way and stays self contained.
>> Is this goal possible to achieve ?
>
>For all situations, I don't think so - what about the compiler for
>example?  NetBSD 1.3.3 used gcc 2.7.2.2 and -current of the time was
>using egcs 1.1.<something>.  The same would more-or-less apply to just
>building a release - what if you were building 1.4.1 on a 1.4 system?
>By using a DESTDIR you don't scribble on your existing system, but you
>are using the existing system to build the release, which isn't self
>contained...
>
>Simon.
>
>