Re: kernel-package build, is this a problem
stan <stanb@panix.com> writes:
> On Thu, Oct 02, 2003 at 03:43:06PM +0200, Werner Mahr wrote:
>>
>> Am Mittwoch, 1. Oktober 2003 18:32 schrieben Sie:
>> > > make-kpkg modules_image
>> >
>> > Shouldn't that create a .deb for the modules, that I need to dpkg
>> > -i? If so, I can't seem to find it.
>>
>> Sorry, modules_image is only for 3. party modules in
>> /usr/src/modules. Try make-kpkg modules and itz schould work. Try man
>> make-kpkg and scroll many sites downwards, there are all targets
>> described.
>>
>
> Mmm, something still smells fishy hrere. When I do that, it complains about
> not being able to build 12c. Now I had built 12c on a previous kernel, but
> I don't want it on this one. It still seems to be buildign moules in
> /usr/src/modules, rather than in the newly downloaded source tree.
>
> Any ideas what I'm doing wrong here?
I can't find context, but:
-- make-kpkg modules-image looks for directories in /usr/src/modules,
and tries to build a third-party module from each of them;
-- make-kpkg modules does the same, but also GPG-signs the result;
-- you don't need to do either if you've just selected modules in the
kernel configuration, since those modules wind up in the normal
kernel-image package.
It sounds like what's going on is that, at some point, you installed
i2c-source and unpacked /usr/src/i2c.tar.gz, and now 'make-kpkg
modules-image' is going off and building that. That's the expected
behavior. If you don't want i2c or anything else in /usr/src, you're
probably done.
(ObUnstable: if you're running unstable, and trying to build i2c
modules, you really really don't want i2c enabled in the kernel, at
all.)
--
David Maze dmaze@debian.org http://people.debian.org/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
Reply to: