Re: compile error with 2.6.7-rc3-mm1

[Paul Jackson]

> okay, I have the "Bad" one. Whatever that means, it seems bad :)

Ok - that's progress.

Then whatever cpumask.h file you are using to compile that code does not
have the fix you think it has.

If you're still stuck, send the output of doing the four commands:

    rm -f drivers/perfctr/x86.i
    make V=1 drivers/perfctr/x86.i | fmt -s
    grep -2 define.CPU_MASK_NONE include/linux/cpumask.h
    grep -2 old_mask.= drivers/perfctr/x86.i

By way of example, when I do these four commands, I get:

    $ rm -f drivers/perfctr/x86.i
    $ make V=1 drivers/perfctr/x86.i | fmt -s
    make -f scripts/Makefile.build obj=scripts/basic
    make -f scripts/Makefile.build obj=scripts
    make -f scripts/Makefile.build obj=drivers/perfctr drivers/perfctr/x86.i
      gcc -E -Wp,-MD,drivers/perfctr/.x86.i.d -nostdinc -iwithprefix
      include -D__KERNEL__ -Iinclude  -Wall -Wstrict-prototypes
      -Wno-trigraphs -fno-strict-aliasing -fno-common -pipe
      -msoft-float -mpreferred-stack-boundary=2  -march=pentium4
      -mregparm=3 -Iinclude/asm-i386/mach-default -O2 -fomit-frame-pointer
      -DKBUILD_BASENAME=x86 -DKBUILD_MODNAME=x86   -o drivers/perfctr/x86.i
      drivers/perfctr/x86.c
    $ grep -2 define.CPU_MASK_NONE include/linux/cpumask.h
    #endif

    #define CPU_MASK_NONE                                                   \
    ((cpumask_t){ {                                                         \
	    [0 ... BITS_TO_LONGS(NR_CPUS)-1] =  0UL                         \
    $ grep -2  old_mask.= drivers/perfctr/x86.i
	    cpumask_t old_mask;

	    old_mask = ((cpumask_t){ { [0 ... (((8)+32 -1)/32)-1] = 0UL } });
	    clear_perfctr_cpus_forbidden_mask();



-- 
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <pj@xxxxxxx> 1.650.933.1373
-
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/