On 8/4/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>
> On Aug 4 2007 11:34, Russell Harmon wrote:
> >>
> >> Speaking of which, the modules_install target is not right. It should
> >> (ideally) be something like
> >>
> >>         make -C ${yourkerneldir} M=$$PWD modules_install;
> >>
> >>
> >>         Jan
> >> --
> >>
> >Hmm, I never noticed it because I patch my kernel, but for me, the
> >makefile (local.mk, not mine) is not building the module correctly. It
> >leaves me with a dead aufs.ko symlink and nothing else =(. Trying to
> >figure that out before I make the (correct) changes you suggested.
>
> I've got this in my rpm specfile:
>
>         make -f local.mk KDIR=/usr/src/linux-obj/%_target_cpu/$flavor
>         modules_install
>
> that seems to work too
>
>         Jan
> --
>
Hmm, that's really weird, the only thing that command does is call the
kernel's Makefile, and when I do that with "make -f local.mk
KDIR=/usr/src/linux", I get

kiki aufs # make -f local.mk KDIR=/usr/src/linux
/usr/bin/make -C /usr/src/linux M=/root/src/kernel/aufs/fs/aufs modules
make[1]: Entering directory `/usr/src/linux-2.6.22-kamikaze5'
  Building modules, stage 2.
  MODPOST 0 modules
make[1]: Leaving directory `/usr/src/linux-2.6.22-kamikaze5'
test ! -e aufs.ko && ln -s fs/aufs/aufs.ko aufs.ko || :
ln: creating symbolic link `aufs.ko': File exists

Then if I call the kernel's Makefile directory directly with V=1, I
don't get any more useful info =(

kiki aufs # /usr/bin/make -C /lib/modules/2.6.22-kamikaze5/build
M=/root/src/kernel/aufs/fs/aufs V=1 modules
make: Entering directory `/usr/src/linux-2.6.22-kamikaze5'
test -e include/linux/autoconf.h -a -e include/config/auto.conf || (
         \
        echo;                                                           \
        echo "  ERROR: Kernel configuration is invalid.";               \
        echo "         include/linux/autoconf.h or
include/config/auto.conf are missing.";      \
        echo "         Run 'make oldconfig && make prepare' on kernel
src to fix it.";  \
        echo;                                                           \
        /bin/false)
mkdir -p /root/src/kernel/aufs/fs/aufs/.tmp_versions
rm -f /root/src/kernel/aufs/fs/aufs/.tmp_versions/*
/usr/bin/make -f scripts/Makefile.build obj=/root/src/kernel/aufs/fs/aufs
  Building modules, stage 2.
/usr/bin/make -f /usr/src/linux-2.6.22-kamikaze5/scripts/Makefile.modpost
  scripts/mod/modpost -m  -i
/usr/src/linux-2.6.22-kamikaze5/Module.symvers -I
/root/src/kernel/aufs/fs/aufs/Module.symvers -o
/root/src/kernel/aufs/fs/aufs/Module.symvers -w
make: Leaving directory `/usr/src/linux-2.6.22-kamikaze5'

What exactly is /usr/src/linux-obj/%_target_cpu/$flavor ? Is that the
base of your kernel sources?

~Russ

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Reply via email to