1 |
On Wed, 2004-10-27 at 22:01 +0100, Stuart Herbert wrote: |
2 |
|
3 |
[snip] |
4 |
|
5 |
> The linux-headers package is installed into the /usr/src/linux tree. If you |
6 |
> already have a kernel unpacked there, linux-headers will happily overwrite |
7 |
> the header files. |
8 |
|
9 |
Er, are you sure? |
10 |
|
11 |
kerin@kerfy ~ $ qpkg -l -nc linux26-headers | cut -d/ -f1-4 | uniq |
12 |
sys-kernel/linux26-headers-2.6.8.1 |
13 |
CONTENTS: |
14 |
/usr |
15 |
/usr/include |
16 |
/usr/include/linux |
17 |
/usr/include/asm-generic |
18 |
/usr/include/asm |
19 |
|
20 |
It's been that way since time immemorial in Gentoo I believe (and |
21 |
rightly so ;). |
22 |
|
23 |
> |
24 |
> Personally, I have /usr/src/linux pointing to my kernel source tree, and I use |
25 |
> emerge's inject option to make portage think that linux-headers is already |
26 |
> installed (so that it doesn't try to overwrite). |
27 |
|
28 |
To each their own, but I find the notion of such an arrangement a little |
29 |
unnerving. The point of the linux-headers package is to provide |
30 |
consistent headers that don't change with the wind. For a build process |
31 |
to use the headers of the currently "active" kernel is a mistake, in my |
32 |
view (there were debates many moons ago in the forums which appear to |
33 |
support that, not to mention the infamous Linus post). Am I missing |
34 |
something? |
35 |
|
36 |
Regards, |
37 |
|
38 |
-- Kerin Francis Millar |