On Tue, Jul 21, 2009 at 7:07 PM, Bernhard Reutner-Fischer<[email protected]> wrote: >>Yes. I want to do that. I set up KERNEL_HEADERS so that uclibc >>build machinery should know where it is. The proof is that >>"make" succeeds. >> >>So uclibc does not require kernel headers to be installed >>into any particular directory, it is working with >>kernel headers installed in any directory, as long as it is >>specified by KERNEL_HEADERS. >> >>Yet, "make check" does not work. It's a bug. > > The proper thing to do here is to setup your toolchain to include > that extra include-dir: > For properly setup sysroot-enabled toolchains the kernel-headers > are already installed in the sysroot. Likewise toolchains configured > not to use sysroot (you shouldn't do this anyway nowadays) have to > specify that directory as include-dir in their c(pp) flags. >> >>Feel free to fix the bug in any way you feel comfortable with. > > In my POV this is a configuration issue and not libc's business.
Then why do we have KERNEL_HEADERS? -- vda _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
