Re: Bug#336732: /lib/modules/*/build symlink should be ignored when checking if kernel is installed
On Sun, Nov 06, 2005 at 10:57:13AM -0600, Manoj Srivastava wrote:
> > There is no reason that the linux-headers packages could not be used
> > to build out-of-tree modules using the symlink, without having the
> > linux-image installed, so this doesn't work, even though it looks
> > like a seducing proposal.
>
> Third party modules which have been integrated into Debian can
> still be built, without the linux-image installed, by
> a) cd /usr/src/kernel-headers-foo, call make-kpkg
> b) KSRC=/usr/src/kernel-headers-foo, call make-kpkg
Yeah, hear yourself, because you don't feel like adding a simple exception to
the check for build, or do a find -name \*.ko as Martin suggested, each and
all the packaged modules need to be modified, as well as all third party
module which are not packaged and depend on the build symlink working.
> All the other third party modules I have seen look for
> /lib/modules/$(uname -r)/build; which implies that the kernel image
> is installed, since it is running, and thus the postint.d scripts
> would already have been called.
It does not. This is the right way to search for those modules, and it implies
the kernel headers and remaininig infrastucture is there, *NOT* the
kernel-image.
> So, we are talking about modules that do not work with
> kernel-package, which have not been integrated into debian, and yet
> need to build against a version of the image package not installed. I
> know of two such modules, nvidia, and vmware, and at least
> vmware-config.pl asks where to find the headers, and people can
> provide that.
No, you have decided to close your eyes on the real problem and make things
difficult to us just because of what you feel is right. Please don't.
Also, see the thread on debian-project about asking vmware to start building
modules for the official kernel images, your way of doing will make this more
difficult, and for what gain ? That is the real question, what do you really
intent by breaking the way the build symlink is now and should be working ?
Friendly,
Sven Luther
Reply to: