Re: [PATCH] kbuild: let object files depend on recordmcount insteadof its sources

From: Steven Rostedt
Date: Fri Oct 07 2011 - 14:52:54 EST

On Fri, 2011-10-07 at 20:04 +0200, Uwe Kleine-König wrote:

> Works for me with 3ee72ca + my patch doing:
> make -C /path/to/my/linux/src/dir defconfig O=$(pwd)
> make -j 6
> If you tell me your exact setup I'll try to reproduce and fix.

I just tried again with the same results. Here:

$ cd git
$ git clone nobackup/linus.git -s -l tmp.git
Cloning into tmp.git...
$ cd tmp.git/
$ mkdir /tmp/build
$ patch -p1 < /tmp/rm.patch
patching file scripts/
$ make O=/tmp/build allyesconfig
HOSTCC scripts/basic/fixdep
GEN /tmp/build/Makefile
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --allyesconfig Kconfig
# configuration written to .config
$ make O=/tmp/build
GEN /tmp/build/Makefile
scripts/kconfig/conf --silentoldconfig Kconfig
/home/pub/git/tmp.git/arch/x86/Makefile:81: stack protector enabled but
no compiler support
Using /home/pub/git/tmp.git as source for kernel
GEN /tmp/build/Makefile
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
CC kernel/bounds.s
GEN include/generated/bounds.h
CC arch/x86/kernel/asm-offsets.s
GEN include/generated/asm-offsets.h
CALL /home/pub/git/tmp.git/scripts/
HOSTCC scripts/genksyms/genksyms.o
SHIPPED scripts/genksyms/lex.lex.c
SHIPPED scripts/genksyms/keywords.hash.c
SHIPPED scripts/genksyms/
HOSTCC scripts/genksyms/lex.lex.o
SHIPPED scripts/genksyms/
HOSTCC scripts/genksyms/
HOSTLD scripts/genksyms/genksyms
make[3]: *** No rule to make target `scripts/mod/empty.o', needed by
`scripts/mod/elfconfig.h'. Stop.
make[2]: *** [scripts/mod] Error 2
make[1]: *** [scripts] Error 2
make: *** [sub-make] Error 2

It needs to be a real clean repo, not a make clean.

-- Steve

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at