Re: [Cooker] kernel-headers: why do they install in /usr/include?
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 http://www.chmouel.org --Chmouel
Re: [Cooker] kernel-headers: why do they install in /usr/include?
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
Re: [Cooker] kernel-headers: why do they install in /usr/include?
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 kernels anyway without > reconfiguring > the source tree... (and modifying the Makefile...) for user applications /lib/mod*/*/build is for drivers -- MandrakeSoft Inc http://www.chmouel.org --Chmouel
Re: [Cooker] kernel-headers: why do they install in /usr/include?
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/include/asm -> /usr/src/linux/include/asm > > /usr/include/linux -> /usr/src/linux/include/linux > > > > The "problem" I had was: I had a driver for a controler which was only > > "compilable" with linux-2.2. > > But before I set the symlinks, I always got the headers of 2.4 for the > > compilation process, at least if I didn't want to modify the > > Makefiles... > > compile your program again : > > /lib/module/$(uname -r)/build/ > > which should go to the right kernel 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 kernels anyway without reconfiguring the source tree... (and modifying the Makefile...) So long, Jürgen
Re: [Cooker] kernel-headers: why do they install in /usr/include?
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/include/linux -> /usr/src/linux/include/linux > > The "problem" I had was: I had a driver for a controler which was only > "compilable" with linux-2.2. > But before I set the symlinks, I always got the headers of 2.4 for the > compilation process, at least if I didn't want to modify the > Makefiles... compile your program again : /lib/module/$(uname -r)/build/ which should go to the right kernel -- MandrakeSoft Inc http://www.chmouel.org --Chmouel
[Cooker] kernel-headers: why do they install in /usr/include?
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" I had was: I had a driver for a controler which was only "compilable" with linux-2.2. But before I set the symlinks, I always got the headers of 2.4 for the compilation process, at least if I didn't want to modify the Makefiles... So long, Jürgen
