RE: Where is the file /usr/include/linux/modversions.h ?
Hey All,
I had this same issue when it came to compiling a couple of drivers.
Modversions.h is a file that is created when you run make menuconfig or
oldconfig.
If you're running a standard woody revision, or a more recent thing you'll
need the kernel headers.. that's where modversions.h is found.
so,
apt-get install kernel-headers-kernel#revision.. etc.
If you're running the most up to date kernel, then you'll have to recompile
the kernel (as debian doesn't have the latest headers hanging around, and if
you do it the debian way (which I recommend) you'll have to make the debian
package as follows:
make-kpkg --revision kernel-image kernel-headers
In fact, you can just make the kernel-headers and then do dpkg -i
kernel-headers.deb
That will take care of it...
If you're ever compiling things, it's always good to have those headers
present for certain operations that may required.
let me know how it goes.
Paul Matuszewski
Systems Administration
In Office Networks
-----Original Message-----
From: jjluza [mailto:jjluza@yahoo.fr]
Sent: Monday, September 15, 2003 11:53 AM
To: debian-user@lists.debian.org
Subject: Re: Where is the file /usr/include/linux/modversions.h ?
As I said to Roberto, I notice the same thing, but I don't know how to force
it compiling against kernel source instead of /usr/include... files
and I don't understand why it works before ... it's strange
Le Lundi 15 Septembre 2003 18:09, Torsten Reuss a écrit :
> jjluza wrote:
> >hi all. I try to compile a driver (nvnet) which includes the file
> >/usr/include/linux/module.h. This file should include the file
> >/usr/include/linux/modversions.h, but it desn't exist anymore :/ where
is
> >this file
>
> debian installs a generic set of linux include files in
> /usr/include/linux. While this is a pretty good thing for compiling
> applications, compiling drivers typically requires the include files of
> the linux kernel that you actually have installed. These are typically
> in /usr/src/linux, but basically could be anywhere else where you keep
> kernel source codes.
>
> The correct way of compiling drivers would be that they do not search in
> /usr/include/linux, but in /lib/modules/`uname -r`/build/include/linux,
> because /lib/modules/`uname -r`/build should be a symbolic link to where
> you keep the sourcecode for the kernel you are currently running.
>
> So I recommend you either try and edit the Makefile of your driver to
> change the include path or you can temporarily link /usr/include/linux
> to /lib/modules/`uname -r`/build/include/linux and your driver should
> compile.
>
> Cheers,
> Torsten
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Reply to: