Your message dated 06 May 2005 11:32:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#307858: mol-modules-source assumes is unpacked in
/usr/src/modules/mol
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 5 May 2005 21:52:19 +0000
>From [EMAIL PROTECTED] Thu May 05 14:52:19 2005
Return-path: <[EMAIL PROTECTED]>
Received: from (localhost.localdomain) [81.181.70.10]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DToGY-0003ha-00; Thu, 05 May 2005 14:52:18 -0700
Received: by localhost.localdomain (Postfix, from userid 1000)
id 766543348; Fri, 6 May 2005 00:50:42 +0300 (EEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Eddy Petrisor <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: mol-modules-source assumes is unpacked in /usr/src/modules/mol
Reply-To: [EMAIL PROTECTED]
X-Mailer: reportbug 3.8
Date: Fri, 06 May 2005 00:50:41 +0300
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
RCVD_IN_DSBL autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: mol-modules-source
Version: 0.9.70-17
Severity: normal
I tried to compile my linux kernel with mol modules, but I found that in
a fakeroot environment it failed. I didn't payed too much attention to
it as the mol drivers were a non-critical issue, but I thought of using
them at a later time.
I am using for kernel compilation kernel-package (make-kpkg) in a folder
in my home directory.
After some attempts I have reached to the point that I think that I am
doing everything right while the modules still do not compile.
Error messages during module build attempt follow:
--------------------------------------------------------------------
[EMAIL PROTECTED]:~/debian_work/packages/new/kernel/kernel-source-2.6.9$
fakeroot
[EMAIL PROTECTED]:~/debian_work/packages/new/kernel/kernel-source-2.6.9#
make-kpkg --revision 13 --append-to-version -sleep-pbg4 modules
for module in /usr/src/modules/mol ; do \
if test -d $module; then \
(cd $module; \
if ./debian/rules KVERS="2.6.9-sleep-pbg4"
KSRC="/home/eddy/debian_work/packages/new/kernel/kernel-source-2.6.9" \
KMAINT="Unknown Kernel Package Maintainer"
KEMAIL="[EMAIL PROTECTED]" \
KPKG_DEST_DIR="/home/eddy/debian_work/packages/new/kernel/kernel-source-2.6.9/.."
\
KPKG_MAINTAINER="Unknown Kernel Package
Maintainer" \
ARCH=ppc \
KPKG_EXTRAV_ARG="EXTRAVERSION=-sleep-pbg4"
\
KDREV="13" kdist; then \
echo "Module $module processed fine"; \
else \
echo "Module $module failed."; \
if [ "X" != "X" ]; then \
echo "Perhaps $module does not understand
--rootcmd?"; \
echo "If you see messages that indicate that it is
not"; \
echo "in fact being built as root, please file a
bug "; \
echo "against $module."; \
fi; \
echo "Hit return to Continue?"; \
read ans; \
fi; \
); \
fi; \
done
make[1]: Entering directory `/usr/src/modules/mol'
dh_testdir
/usr/bin/make
make[2]: Entering directory `/usr/src/modules/mol'
/usr/bin/make -C src/kmod
make[3]: Entering directory `/usr/src/modules/mol/src/kmod'
+ Entering Linux
mkdir: cannot create directory `../build': Permission denied
make[4]: *** [make-relbuild] Error 1
make[3]: *** [sub-Linux-all] Error 2
make[3]: Leaving directory `/usr/src/modules/mol/src/kmod'
make[2]: [src/kmod] Error 2 (ignored)
/usr/bin/make -C src/netdriver
make[3]: Entering directory `/usr/src/modules/mol/src/netdriver'
mkdir: cannot create directory `build': Permission denied
make[3]: *** [setup-tree-common] Error 1
make[3]: Leaving directory `/usr/src/modules/mol/src/netdriver'
make[2]: [src/netdriver] Error 2 (ignored)
make[2]: Leaving directory `/usr/src/modules/mol'
touch build-stamp
touch: cannot touch `build-stamp': Permission denied
make[1]: *** [build-stamp] Error 1
make[1]: Leaving directory `/usr/src/modules/mol'
Module /usr/src/modules/mol failed.
Hit return to Continue?
-----------------------------------------------------------------------
After this point It gets back to the bash prompt and there is no mol
driver generated, of course.
As the messages suggest, make is trying to work with the mol drivers at
/usr/src/modules/mol, which is defenetly wrong.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (600, 'testing'), (500, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.9-sleep-pbg4
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages mol-modules-source depends on:
ii gcc 4:3.3.5-3 The GNU C compiler
ii libc6-dev 2.3.2.ds1-21 GNU C Library: Development Librari
ii make 3.80-9 The GNU version of the "make" util
-- no debconf information
---------------------------------------
Received: (at 307858-done) by bugs.debian.org; 6 May 2005 09:32:54 +0000
>From [EMAIL PROTECTED] Fri May 06 02:32:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from alsvidh.mathematik.uni-muenchen.de [129.187.111.42]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DTzCX-0008Kz-00; Fri, 06 May 2005 02:32:53 -0700
Received: by alsvidh.mathematik.uni-muenchen.de (Postfix, from userid 666)
id D7E663A45D; Fri, 6 May 2005 11:32:20 +0200 (CEST)
Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#307858: mol-modules-source assumes is unpacked in
/usr/src/modules/mol
References: <[EMAIL PROTECTED]>
Organization: Lehrstuhl fuer vergleichende Astrozoologie
X-Mahlzeit: Das ist per Saldo Gemuetlichkeit
Reply-To: Jens Schmalzing <[EMAIL PROTECTED]>
From: Jens Schmalzing <[EMAIL PROTECTED]>
Date: 06 May 2005 11:32:20 +0200
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Lines: 18
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Hi,
Eddy Petrisor writes:
> As the messages suggest, make is trying to work with the mol drivers
> at /usr/src/modules/mol, which is defenetly wrong.
This is not a bug in mol-modules-source, but rather the default
behaviour of make-kpkg, which can be changed in a number of ways. All
of them are described in the manpage of make-kpkg, I always set the
environment variable MODULE_LOC to point to the directory where I
unpack the source.
Regards, Jens.
--=20
J'qbpbe, le m'en fquz pe j'qbpbe!
Le veux aimeb et mqubib panz je p=E9zqbpbe je djuz tqtaj!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
