| 1 |
I had countless problems getting stuff to compile against 2.5 because of |
| 2 |
2.4 headers being present in /usr/lib - this madness has to end, is |
| 3 |
there no sane solution to this crap, basically we risk breaking |
| 4 |
something at near random when we upgrade the kernel just because some |
| 5 |
header changed and some program makes an assumption that is wrong like a |
| 6 |
struct that has changed - right? |
| 7 |
|
| 8 |
we need a sane way to work around this - I remember Martin Schlemmer |
| 9 |
once proposing a kernel API to make sure we always had a sane way of |
| 10 |
working with the kernel without including kernel headers in userspace |
| 11 |
which is the cause of many a problem. |
| 12 |
|
| 13 |
- Lovechild |
| 14 |
|
| 15 |
On Sat, 2003-06-21 at 00:40, Svyatogor wrote: |
| 16 |
> On Friday 20 June 2003 19:25, Martin Schlemmer wrote: |
| 17 |
> > |
| 18 |
> > Anyhow, in general in Gentoo, if you compile something like iptable, |
| 19 |
> > nvidia-kernel, alsa, etc, it use the kernel headers in /usr/src/linux, |
| 20 |
> > as it is easier to manage (say you are running kernel from livecd, |
| 21 |
> > but want to compile whatever for your kernel that you will be |
| 22 |
> > booting ...). |
| 23 |
> Exactly, so it shouldn't be installing the headers in /usr/include/linux, |
| 24 |
> which is what linux-headers does. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives