On 11/4/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote: > On Sun, Nov 04, 2007 at 05:50:51PM -0500, Chris Smith wrote: [snip] > But you will see lots of errors. > Oh - and I do not understand what you are trying to achive anyway. > > If you request more help please explain what you are trying to > achive (and I mean more than "getting preprocessed output of all .c files"). > > PS. You need to be in ../targ directory when executing the commands > but after a Makefile has been generated. > > Sam > rm -rf ../targ/ && mkdir ../targ && make mrproper && cat /proc/config.gz | gunzip > ../targ/.config && make prepare O=../targ && make scripts O=../targ && make O=../targ CFLAGS=-E KBUILD_NOCMDDEP=1 -k
got me most of the way, dying after some time: [omit copious screens] AR lib/lib.a CC [M] lib/crc-ccitt.o CC [M] lib/crc16.o CC [M] lib/libcrc32c.o CC [M] lib/ts_kmp.o CC [M] lib/ts_bm.o CC [M] lib/ts_fsm.o make[2]: Target `__build' not remade because of errors. make[1]: *** [lib] Error 2 CC arch/x86/lib/msr-on-cpu.o LD arch/x86/lib/built-in.o arch/x86/lib/msr-on-cpu.o: file not recognized: File format not recognized make[2]: *** [arch/x86/lib/built-in.o] Error 1 CC arch/x86/lib/bitops_32.o AS arch/x86/lib/checksum_32.o CC arch/x86/lib/delay_32.o AS arch/x86/lib/getuser_32.o CC arch/x86/lib/memcpy_32.o AS arch/x86/lib/putuser_32.o AS arch/x86/lib/semaphore_32.o CC arch/x86/lib/string_32.o CC arch/x86/lib/strstr_32.o CC arch/x86/lib/usercopy_32.o AR arch/x86/lib/lib.a make[2]: Target `__build' not remade because of errors. make[1]: *** [arch/x86/lib] Error 2 make[1]: Target `_all' not remade because of errors. make: *** [sub-make] Error 2 make: Target `_all' not remade because of errors. ---------------------------8<----------------------------- Where was I going with this? I was reading through William von Hagen's "The Definitive Guide to GCC", and I was thinking that some of the debugging things you can add to GCC, to get more information from the source code. Upon deeper inspection, it looks like most of those options apply to C++, alas. Armed with a reduced codebase, it would be easier to run it through indent to tweak the appearance to taste, as well as get through a ctags run more quickly, with less noise data for my configuration. Just a couple of things a mere wannabee might do to shorten the kernel's impressive learning curve, that's all. Best, Chris - 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
