Re: kernel buildsystem error/warning?

[Kumar Gala]

On Sep 23, 2005, at 12:44 AM, Gala Kumar K.-galak wrote:

> On Sep 22, 2005, at 11:49 PM, Randy.Dunlap wrote:
>
>
> > On Thu, 22 Sep 2005 08:45:35 -0500 Kumar Gala wrote:
> >
> >
> >
> > > Sam,
> > >
> > > I was wondering if anyone else is seeing the following error/warning
> > > when building a recent kernel.  This error seems to have been
> > > introduced between 2.6.13 and 2.6.14-rc1:
> > >
> > >    CHK     include/linux/version.h
> > >    CHK     include/linux/compile.h
> > >    CHK     usr/initramfs_list
> > > /bin/sh: line 1: +@: command not found
> > >    CHK     include/linux/compile.h
> > >    UPD     include/linux/compile.h
> > >    CC      init/version.o
> > >    LD      init/built-in.o
> > >    LD      vmlinux
> > >    SYSMAP  System.map
> > >
> > >
> > > I'm building a cross compiled ARCH ppc kernel on an x86 host.  I
> > > tried using git bisect to track down the error but for some  
> > > reason it
> >
> >
> >
> > > ended up referencing a change before 2.6.13 which I really dont
> > > understand.
> > >
> > > Anyways, let me know if you need more info on this.
> >
> > I don't see the error message.  Do you have anything (added) to
> > usr/initramfs_list ?  (of course, the error messsage doesn't have
> > to be coming from that file at all)
>
> Nope. Hmm, after a little more debug it appears to be an issue with
> "if_changed_rule" in scripts/Kbuild.include. If I remove the '@' in
> front of the "set -e" I get the following:
>
>    CHK     include/linux/version.h
>    CHK     include/linux/compile.h
>    CHK     usr/initramfs_list
> set -e;         +@ echo '  GEN     .version' && set -e; if [ ! -
> r .version ]; then rm -f .version; echo 1 >.version; else
> mv .version .old_version; expr 0$(cat .old_version) + 1 >.version;
> fi; make -f scripts/Makefile.build obj=init
> /bin/sh: line 1: +@: command not found
>    CHK     include/linux/compile.h
>    UPD     include/linux/compile.h
> set -e;           echo '  CC      init/version.o'; powerpc-unknown-
> linux-gnu-gcc -m32 -Wp,-MD,init/.version.o.d  -nostdinc -isystem /
> _TOOLS_/dist/gnu-gcc-3.4.3-binutils-2.15-powerpc-unknown-linux-gnu/
> i686-pc-linux2.4/lib/gcc/powerpc-unknown-linux-gnu/3.4.3/include -
> D__KERNEL__ -Iinclude  -Iarch/ppc -Iarch/ppc/include -Wall -Wundef -
> Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -
> ffreestanding -O2     -fomit-frame-pointer -Iarch/ppc -msoft-float -
> pipe -ffixed-r2 -mmultiple -Wa,-me500 -Wdeclaration-after-
> statement     -DKBUILD_BASENAME=version -DKBUILD_MODNAME=version -c -
> o init/version.o init/version.c;  scripts/basic/fixdep
> init/.version.o.d init/version.o 'powerpc-unknown-linux-gnu-gcc -m32 -
> Wp,-MD,init/.version.o.d  -nostdinc -isystem /_TOOLS_/dist/gnu-
> gcc-3.4.3-binutils-2.15-powerpc-unknown-linux-gnu/i686-pc-linux2.4/
> lib/gcc/powerpc-unknown-linux-gnu/3.4.3/include -D__KERNEL__ -
> Iinclude  -Iarch/ppc -Iarch/ppc/include -Wall -Wundef -Wstrict-
> prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -
> ffreestanding -O2     -fomit-frame-pointer -Iarch/ppc -msoft-float -
> pipe -ffixed-r2 -mmultiple -Wa,-me500 -Wdeclaration-after-
> statement     -DKBUILD_BASENAME=version -DKBUILD_MODNAME=version -c -
> o init/version.o init/version.c' > init/.version.o.tmp; rm -f
> init/.version.o.d; mv -f init/.version.o.tmp init/.version.o.cmd
>    CC      init/version.o
>    LD      init/built-in.o
>    LD      vmlinux
>    SYSMAP  System.map
>
> I'm guessing the +@ echo... is what's getting me, not to figure out
> why that's happening.
>
> - kumar

After some more debug it appears that define rule_vmlinux__ is what's  
causing this and in my .config CONFIG_KALLSYMS is not defined.

Not sure if that will help.  If I enable CONFIG_KALLSYMS the "error"  
goes away (which makes sense based on the rule_vmlinux__) define.

- kumar

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/