Where is install_kernel_headers? (+ git web interface question)

Denys Vlasenko vda.linux at googlemail.com
Tue Jul 21 16:17:02 UTC 2009


On Tue, Jul 21, 2009 at 5:31 PM, Bernhard
Reutner-Fischer<rep.dot.nop at gmail.com> wrote:
> On Tue, Jul 21, 2009 at 05:21:59PM +0200, Denys Vlasenko wrote:
>>I am trying to run the testsuite.
>
> $ make help | grep testsuite
>  check                 - run testsuite
>  test_compile          - compile testsuite binaries

# make check
make[2]: Nothing to be done for `compile'.
  TEST_LINK assert/ assert
In file included from ../../install_dir/usr/include/signal.h:354,
                 from assert.c:14:
../../install_dir/usr/include/bits/sigcontext.h:31:29: error:
asm/sigcontext.h: No such file or directory
In file included from assert.c:14:
../../install_dir/usr/include/signal.h:357: warning: 'struct
sigcontext' declared inside parameter list
../../install_dir/usr/include/signal.h:357: warning: its scope is only
this definition or declaration, which is probably not what you want
make[2]: *** [assert] Error 1
make[1]: *** [_dircompile_assert] Error 2
make: *** [test_compile] Error 2


> Mike removed it since it's not libc's business to install kernel
> headers (and i agree with him, fwiw).

Ok, then how can I test uclibc _before_ I install it?
I can build it becuase I have correctly set up KERNEL_HEADERS="xxx",
but "make check" does not work.


> 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

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.

--
vda


More information about the uClibc mailing list