On Tue, Jul 21, 2009 at 06:48:08PM +0200, Denys Vlasenko wrote: >On Tue, Jul 21, 2009 at 6:34 PM, Bernhard >Reutner-Fischer<[email protected]> wrote: >> On Tue, Jul 21, 2009 at 06:17:02PM +0200, Denys Vlasenko wrote: >>>> You have to have a properly installed set of kernel-headers before >>>> you build the libc, really. >>> >>>This adds yet another step into cross-compilation. >>> >>>Up to today, I was able to: >>>1. build+install cross-compiling toolchain, >>>2. build+install uclibc, >>>3. build+install userspace, >>> >>>and now I need to add >>>2.5 install kernel headers >> >> I don't quite understand. At this spot you should already have >> the kernel-headers installed somewhere, why don't you use them? > >I don't have them installed, not in any permanent location. >They are just sitting in a directory alongside the uclibc >build directory. My .config contains this: > >KERNEL_HEADERS="../linux-2.6.27.6/usr/include" > >>>Can I have an option to not do it? It's not like I force you >>>to use "make install_kernel_headers", I just want to be able >>>to use it myself. >> >> I don't see why libc should deal with fiddling stuff from other >> packages, that's not clean. As said above, use the headers that >> you previously installed somewhere. > >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. _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
