Hard wired Linux header paths?

[Bernhard Reutner-Fischer]

On Wed, Mar 17, 2010 at 01:54:45PM -0400, Ersin Akinci wrote:
>Sorry, that was a little unclear: I was running make install on uClibc after
>having built uClibc.

please do not top-post.
>
>-Ersin
>
>On Wed, Mar 17, 2010 at 1:53 PM, Ersin Akinci <ersin.akinci at gmail.com>wrote:
>
>> Hi all,
>>
>> I was running "make install" after compiling and I wanted to install to a
>> temporary root directory (that is, a random subdir on my system that I'm
>> treating as a root dir for creating an image) that I had already installed
>> my Linux headers to, the same ones which I had told uClibc to use during its
>> compile.  Before installing, however, I cleaned out the directory, thus
>> removing the headers so that I could create a tar file with just the uClibc
>> install for backup purposes, but make install wouldn't run without the
>> headers in place.  What's the reason for this?  Is make install
>> hardwiring/hardwired to some header paths?

uClibc needs kernel headers to generate headers.

If you want to install uClibc into a separate, empty directory that
you can tar, then install it to that separate directory.

make PREFIX=/my/rootdir install_headers
make PREFIX=/some/where/else install_headers