[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#330081: marked as done (linux-headers-2.6.12-1-686: Doesn't provide correct module installation directory, needs LOCALVERSION override)

Your message dated Mon, 30 Oct 2006 17:20:15 +0100
with message-id <20061030162015.GD32488@nancy>
and subject line Bug#330081: Doesn't provide correct module installation directory, needs LOCALVERSION override
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: linux-headers-2.6.12-1-686
Severity: minor
Version: 2.6.12-6

A module collection that just uses:
@$(MAKE) -C $(KERNEL_SOURCES) SUBDIRS=$(shell pwd) modules_install
to install its kernel modules will try to put its output in
/lib/modules/2.6.12/extra
instead of
/lib/modules/2.6.12-1-686/extra

This is because scritps/Makefile.modinst uses MODLIB, supplied from
Makefile as
$(INSTALL_MOD_PATH)/lib/modules/$(KERNELRELEASE),
where KERNELRELEASE is the culprit, as it is built from
$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)$(LOCALVERSION)
and EXTRAVERSION is not set in the Makefile, as it is shared across all
of 2.6.12-1

There are two apparent mechanisms to deal with this. The package has a
.config, in which a CONFIG_LOCALVERSION could be set to get the correct
behaviour.

Alternatively, a file called localversion-debian (actually
localversion*) could be created, which could contain the same string.

Either of these would cause modules to be able to install in the correct
place without any user intervention. (ie if they can find the headers,
they'll install in the right place)

(I realise this is not the actual package at fault, but I'm not familiar
with the kernel-team's build or triage procedures, so I'll leave it to
you to put this against the right package.)


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (950, 'unstable'), (900, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

-- 
Paul "TBBle" Hampson, Paul.Hampson@Anu.edu.au
8th year CompSci/Asian Studies student, ANU

Shorter .sig for a more eco-friendly paperless office.

Attachment: pgpXNJFM5MbtM.pgp
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Version: 2.6.18-1

On Sat, 28 Oct 2006, Paul TBBle Hampson wrote:

> I can confirm this bug doesn't affect 2.6.18-1-powerpc (2.6.18-3) but
> I honestly can't say I noticed when it was fixed, so I won't tag this
> myself.

thanks closing with verified headers :)
 
-- 
maks

--- End Message ---
Reply to: