nanogui: Trouble building Microwindows for MIPS target
Subject:
Re: Trouble building Microwindows for MIPS target
From:
Joe deBlaquiere ####@####.####
Date:
15 Feb 2001 03:55:52 -0000
Message-Id: <3A8B552D.7090202@redhat.com>
Scott A McConnell wrote:
> from
> /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/include/limits.h:117,
> from
> /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/include/syslimits.h:7,
> from
> /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/include/limits.h:11,
> from scr_fb.c:13:
> /usr/include/bits/local_lim.h:27: warning: No include path in which to find
> linux/limits.h
> scr_fb.c:14: warning: No include path in which to find linux/fb.h
> scr_fb.c:15: warning: No include path in which to find linux/kd.h
> scr_fb.c:16: warning: No include path in which to find linux/vt.h
> In file included from /usr/include/sys/ioctl.h:27,
> from scr_fb.c:24:
> /usr/include/bits/ioctls.h:24: warning: No include path in which to find
> asm/ioctls.h
> In file included from /usr/include/sys/ioctl.h:30,
> from scr_fb.c:24:
> /usr/include/bits/ioctl-types.h:25: warning: No include path in which to find
> asm/ioctls.h
>
> .......more like the above .....
>
>
>
> I still would like to understand why I am getting the above warnings.
>
Looks to me like the kernel headers are not installed (or symlinked) to
you <cross_sysroot>/usr/include directory. There was a discussion some
time back about putting a 'make install-headers' into the Linux kernel
build for just such occasions. You need to make sure that the linux and
asm-mips directories are available in the default include path and that
include/asm points to include/asm-mips. (you also want to make sure that
you have generated linux/version.h before you copy anything to the
include tree if you're going to copy).
I have also seen kernel header RPMs around, but I am pretty paranoid to
make sure that the development kernel I'm using is the one used in the
compiler build process and in the cross-root directory.
Hope this helps... :)
--
Joe
