Your message dated Fri, 07 Nov 2008 09:36:40 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#504770: [kernel-package] USER INSTRUCTIONS for 
building add on modules fail at step 6
has caused the Debian Bug report #504770,
regarding [kernel-package] USER INSTRUCTIONS for building add on modules fail 
at step 6
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
504770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504770
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: kernel-package
Version: 11.0011
Severity: normal

I'm unable to follow the USER INSTRUCTIONS in README.modules. For several 
modules, step 6 fails with a permission problem:

$ LANG=C make-kpkg modules_image
exec debian/rules  DEBIAN_REVISION=2.6.26-10.00.Custom  modules_image
for module in /usr/src/modules/nvidia-kernel ; do                       \
          if test -d  $module; then                                \
            (cd $module;                                          \
              if ./debian/rules KVERS="2.6.26" 
KSRC="/home/chealer/sources/linux-source-2.6.26" \
                             KMAINT="Unknown Kernel Package Maintainer" 
KEMAIL="[EMAIL PROTECTED]"      \
                             
KPKG_DEST_DIR="/home/chealer/sources/linux-source-2.6.26/.."       \
                             KPKG_MAINTAINER="Unknown Kernel Package 
Maintainer"        \
                             KPKG_EXTRAV_ARG=""        \
                             ARCH="i386"         \
                             KDREV="2.6.26-10.00.Custom" kdist_image; 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;                                                   \
             );                                                    \
          else                                                      \
               echo "Module $module does not exist";               \
               echo "Hit return to Continue?";                      \
          fi;                                                       \
        done
make[1]: Entering directory `/usr/src/modules/nvidia-kernel'
echo "ROOT_CMD = "
ROOT_CMD =
/usr/bin/make -w -f debian/rules binary_modules
make[2]: Entering directory `/usr/src/modules/nvidia-kernel'
# select which makefile to use.
rm -f /usr/src/modules/nvidia-kernel/Makefile || true
rm: cannot remove `/usr/src/modules/nvidia-kernel/Makefile': Permission denied
if [ 6 = 6  ]; then \
             ln -s Makefile.kbuild Makefile ; \
        fi
ln: creating symbolic link `Makefile': File exists
make[2]: *** [config.Makefile] Error 1
make[2]: Leaving directory `/usr/src/modules/nvidia-kernel'
make[1]: *** [kdist_image] Error 2
make[1]: Leaving directory `/usr/src/modules/nvidia-kernel'
Module /usr/src/modules/nvidia-kernel failed.
Hit return to Continue

--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.26-1-amd64

Debian Release: lenny/sid
  990 testing         security.debian.org 
  990 testing         gulus.usherbrooke.ca 
  500 unstable        gulus.usherbrooke.ca 

--- Package information. ---
Depends                  (Version) | Installed
==================================-+-=============
perl                               | 5.10.0-16
dpkg                      (>= 1.4) | 1.14.22
dpkg-dev              (>= 1.4.0.9) | 1.14.22
gcc                                | 4:4.3.2-2
 OR c-compiler                     | 
make                  (>= 3.80-10) | 3.81-5
po-debconf                         | 1.0.15
gettext                            | 0.17-4
file                               | 4.26-1
debianutils              (>= 2.30) | 2.30
binutils                 (>= 2.12) | 2.18.1~cvs20080103-7
util-linux              (>= 2.10o) | 2.13.1.1-1
module-init-tools      (>= 0.9.10) | 3.4-1





--- End Message ---
--- Begin Message ---
Hi,

        You need to setup the modules path to a place you have write
 permission to, and set the MODULE_LOC env variable accordingly.
 Or else, file a bug on the module package for not using the ROOR_CMD
 env variable to become root.

        On my machine, /usr is mounted ro, so this run-as-root solution
 ill not work in such cases.

        manoj
-- 
A man who fishes for marlin in ponds will put his money in Etruscan
bonds.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


--- End Message ---

Reply via email to