/usr/include *poof!*

[J.L.WOOD]

I've seen this before and the cause is that there are no
files from /usr/include in the foundation set.  /usr/include
is created by loading the development set.  What happened to
us was that we `installed from floppy' a package or two that
had .h files in them.  The Install script had something
of the form:

	mv xyz.h /usr/include

which would produce the effect we encountered.  The message:

Load the development set immediately after the foundation set
if you are going to put it on the machine at all; otherwise,
don't worry.


Joe Wood
lznv!jlw