On Sun, Dec 09, 2007 at 11:34:24PM +0100, Sam Ravnborg wrote: > On Mon, Nov 26, 2007 at 11:25:50AM -0800, Randy Dunlap wrote: > > Hi Sam, > > > > Have you had a chance to look at this kbuild issue? > > > > > > "make -B [all]" (after make *config) produces this (exits with error): > > > > linux-2.6.24-rc2-git5> make -B [] > > gcc -m elf_x86_64 /tester/linsrc/linux-2.6.24-rc2-git5/arch/x86/Makefile.o > > -o /tester/linsrc/linux-2.6.24-rc2-git5/arch/x86/Makefile
It seems, that target pattern > -# No need to remake these files > -$(srctree)/arch/x86/Makefile%: ; > - generates all GNUmake's implicit targets and runs (-B feature/bug?) their implicit rules; *.o implicit target seems to be the first... #!shell [EMAIL PROTECTED]:/tmp$ > file [EMAIL PROTECTED]:/tmp$ make -d -f file | head -n 16 GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for x86_64-pc-linux-gnu Reading makefiles... Reading makefile `file'... Updating makefiles.... Considering target file `file'. Looking for an implicit rule for `file'. Trying pattern rule with stem `file'. Trying implicit prerequisite `file.o'. Trying pattern rule with stem `file'. Trying implicit prerequisite `file.c'. [EMAIL PROTECTED]:/tmp$ ## > > gcc: /tester/linsrc/linux-2.6.24-rc2-git5/arch/x86/Makefile.o: No such file > > or directory > > gcc: no input files > > make: *** [/tester/linsrc/linux-2.6.24-rc2-git5/arch/x86/Makefile] Error 1 > > > > Took a look now. > Following patch fixes it. Problem is that I have not understood > fully WHY this patch fixes this issue. > The change to the top-level Makefile is cosmetic only, the real fix > is the change in arch/x86/Makefile > > Anyone else that can sched some light on this? > > I recall I put that rule in as a simple performance optimization. > > Sam ____ - To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
