Andrej Borsenkow <[EMAIL PROTECTED]> writes:
> On 10 Apr 2001, Chmouel Boudjnah wrote:
>
> >
> > for user applications /lib/mod*/*/build is for drivers
> >
>
> Why additional indirection and not simply /usr/src/linux-`uname -r`?
to have the release also..
--
MandrakeSoft Inc
On 10 Apr 2001, Chmouel Boudjnah wrote:
>
> for user applications /lib/mod*/*/build is for drivers
>
Why additional indirection and not simply /usr/src/linux-`uname -r`?
-andrej
Jürgen Zimmermann <[EMAIL PROTECTED]> writes:
> Ok. But this raises one more question:
> Why are the asm/linux-Includes both provided in kernel-headers AND
> kernel-source?
> Couldn't the "few" different files be generated on demand, especially
> the
> module versions, which do not work for SMP
Chmouel Boudjnah wrote:
>
> Jürgen Zimmermann <[EMAIL PROTECTED]> writes:
>
> > Hello,
> > I wonder why the kernel-headers for 2.4 kernels do install in
> > /usr/include?
> > Isn't it sufficient to install them in /usr/src/linux-2.4.*/include
> > and set appropriate symlinks from
> > /usr/includ
Jürgen Zimmermann <[EMAIL PROTECTED]> writes:
> Hello,
> I wonder why the kernel-headers for 2.4 kernels do install in
> /usr/include?
> Isn't it sufficient to install them in /usr/src/linux-2.4.*/include
> and set appropriate symlinks from
> /usr/include/asm -> /usr/src/linux/include/asm
> /usr/
Hello,
I wonder why the kernel-headers for 2.4 kernels do install in
/usr/include?
Isn't it sufficient to install them in /usr/src/linux-2.4.*/include
and set appropriate symlinks from
/usr/include/asm -> /usr/src/linux/include/asm
/usr/include/linux -> /usr/src/linux/include/linux
The "problem"
