Hello,

More than anything, a question on correct direction.

----

It would appear that the directory `sys/lib/libkern' assumes that the
compiler has access to `installed' header files (for example
quad.h:#include <limits.h>).  If cross compiling, this may not be the
case.

In the patch below I assume that the uninstalled include directory is
online several levels up and hence just add it to the includes.

I also added the -DKERNEL to force into scope several of the kernel
macro's and prototypes to be defined (is it a kernel only library?).

Any sensible comments?

----

A follow on question about libkern is should it be expanded to include
portable C implementations of things like bzero/bcopy/copyin/copyout
etc?  The latter two would call upon non portable lower level functions
implemented in locore or where ever.  In the case of bcopy, is something
like:

	#include "../../lib/libc/string/bcopy.c"

acceptable?

----

			Andrew


*** nbsd/sys/lib/libkern/SRC/Makefile	Tue Feb 14 22:12:29 1995
--- nbsd/sys/lib/libkern/Makefile	Sat Jun 17 17:06:28 1995
***************
*** 3,9 ****
  LIB=	kern
  NOPIC=
  OBJMACHINE=
! CFLAGS= -O3 -I${.CURDIR} -Imachine/.. -I. -I${.CURDIR}/../..
  
  machine-links:
  	-@rm -f machine && \
--- 3,9 ----
  LIB=	kern
  NOPIC=
  OBJMACHINE=
! CFLAGS= -O3 -I${.CURDIR} -Imachine/.. -I. -I${.CURDIR}/../..
-I${.CURDIR}/../../../include -DKERNEL
  
  machine-links:
  	-@rm -f machine && \