On 9/3/06, Sam Ravnborg <[email protected]> wrote:
> On Sun, Sep 03, 2006 at 02:16:05PM -0700, Miles Lane wrote:
> > On 9/3/06, Sam Ravnborg <[email protected]> wrote:
> > >
> > >[ketchup -g 2.6-mm; make defconfig; make menuconfig]
> > >
> > >[sam@neptun mm]$ grep LOCKDEP .config
> > >CONFIG_LOCKDEP_SUPPORT=y
> > >CONFIG_LOCKDEP=y
> > >CONFIG_DEBUG_LOCKDEP=y
> > >[sam@neptun mm]$ make
> > > CHK include/linux/version.h
> > > CHK include/linux/utsrelease.h
> > > CHK include/linux/compile.h
> > > MODPOST vmlinux
> > >Kernel: arch/i386/boot/bzImage is ready (#3)
> > > Building modules, stage 2.
> > > MODPOST 1 modules
> > >[sam@neptun mm]$ touch kernel/lockdep_internals.h
> > >[sam@neptun mm]$ make
> > > CHK include/linux/version.h
> > > CHK include/linux/utsrelease.h
> > > CHK include/linux/compile.h
> > > CC kernel/lockdep.o
> > > CC kernel/lockdep_proc.o
> > >
> > >Works for me?
> > >
> > >Miles - can you double check that you have CONFIG_LOCKDEP defined.
> >
> > Ah, I suspect I was being a dufus. I was looking for the exact
> > filename, since I rarely receive patches for anything other than C
> > files. I probably overlooked it. I'm very sorry to have bothered
> > you. BTW, yes, I had it defined.
>
> No problem.
> Can I request you to do a follow-up post to the mail at lkml
> just so people do not start to mistrust kbuild.
>
> It takes quiet some time to gain trust but only little to loose
> it again so it would be very nice to close this one in public.
Sure. I didn't notice you had dropped LKML off the CC list in your reply.
Hey everyone, mea culpa. KBuild is working fine! :-)
--
VGER BF report: U 0.500013