* Andrew Morton ([EMAIL PROTECTED]) wrote: > On Thu, 15 Feb 2007 17:01:27 +0100 > Tilman Schmidt <[EMAIL PROTECTED]> wrote: > > > Trying to build 2.6.20-mm1 on i386 with C=1, sparse 0.2 chokes > > on arch/i386/kernel/i8253.c: > > > > CHECK arch/i386/kernel/i8253.c > > linux/marker.h: No such file or directory > > include/linux/jiffies.h:18:5: warning: undefined preprocessor identifier > > 'CONFIG_HZ' > > include/linux/jiffies.h:20:7: warning: undefined preprocessor identifier > > 'CONFIG_HZ' > > include/linux/jiffies.h:22:7: warning: undefined preprocessor identifier > > 'CONFIG_HZ' > > include/linux/jiffies.h:24:7: warning: undefined preprocessor identifier > > 'CONFIG_HZ' > > include/linux/jiffies.h:26:7: warning: undefined preprocessor identifier > > 'CONFIG_HZ' > > include/linux/jiffies.h:28:7: warning: undefined preprocessor identifier > > 'CONFIG_HZ' > > include/linux/jiffies.h:30:7: warning: undefined preprocessor identifier > > 'CONFIG_HZ' > > include/linux/jiffies.h:33:3: error: You lose. > > include/linux/jiffies.h:225:5: error: bad constant expression > > include/asm/module.h:64:2: error: unknown processor family > > include/asm/processor.h:82:30: error: undefined identifier > > 'CONFIG_X86_L1_CACHE_SHIFT' > > include/asm/processor.h:82:30: error: bad constant expression type > > arch/i386/kernel/i8253.c:120:16: error: Expected ; at end of declaration > > arch/i386/kernel/i8253.c:120:16: error: got pit_read > > arch/i386/kernel/i8253.c:128:2: error: Trying to use reserved word 'do' as > > identifier > > arch/i386/kernel/i8253.c:128:2: error: Expected ; at end of declaration > > arch/i386/kernel/i8253.c:128:2: error: got { > > [loads of similar messages omitted ...] > > arch/i386/kernel/i8253.c:195:2: error: undefined identifier > > 'clocksource_pit' > > arch/i386/kernel/i8253.c:196:9: error: undefined identifier > > 'clocksource_register' > > arch/i386/kernel/i8253.c:41:7: error: Expected constant expression in case > > statement > > arch/i386/kernel/i8253.c:50:7: error: Expected constant expression in case > > statement > > Me too. It's due to the linux-kernel-markers patches. Mathieu, can you > take a look please?
I will give a deeper look in sparse, but I should say up front that I add this to the root build tree Makefile : LINUXINCLUDE := -Iinclude \ $(if $(KBUILD_SRC),-Iinclude2 -I$(srctree)/include) \ -include include/linux/autoconf.h \ -include linux/marker.h I guess sparse is maybe not using this Makefile or variable ? -- Mathieu Desnoyers Computer Engineering Ph.D. Candidate, École Polytechnique de Montréal OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/