Re: 2.6.13-rc6-mm1

[Andrew Morton]

Rogério Brito <rbrito@xxxxxxxxxx> wrote:
>
> Unfortunately, it seems that current kernels (including vanilla -rc
>  kernels) don't compile correctly on ppc if I have APM emulation enabled,
>  but PMU disabled (only CUDA enabled).
> 
>  Here is what I get from a compilation try:
> 
>  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>  debian:~/kernel/linux# make vmlinux
>    CHK     include/linux/version.h
>  make[1]: `arch/ppc/kernel/asm-offsets.s' is up to date.
>    CHK     include/linux/compile.h
>    CHK     usr/initramfs_list
>    CC      sound/oss/dmasound/dmasound_awacs.o
>  sound/oss/dmasound/dmasound_awacs.c:262: warning: 'struct pmu_sleep_notifier' declared inside parameter list
>  sound/oss/dmasound/dmasound_awacs.c:262: warning: its scope is only this definition or declaration, which is probably not what you want
>  sound/oss/dmasound/dmasound_awacs.c:263: error: variable 'awacs_sleep_notifier' has initializer but incomplete type
>  sound/oss/dmasound/dmasound_awacs.c:264: warning: excess elements in struct initializer
>  sound/oss/dmasound/dmasound_awacs.c:264: warning: (near initialization for 'awacs_sleep_notifier')
>  sound/oss/dmasound/dmasound_awacs.c:264: error: 'SLEEP_LEVEL_SOUND' undeclared here (not in a function)
>  sound/oss/dmasound/dmasound_awacs.c:264: warning: excess elements in struct initializer
>  sound/oss/dmasound/dmasound_awacs.c:264: warning: (near initialization for 'awacs_sleep_notifier')
>  sound/oss/dmasound/dmasound_awacs.c:1424: error: conflicting types for 'awacs_sleep_notify'
>  sound/oss/dmasound/dmasound_awacs.c:262: error: previous declaration of 'awacs_sleep_notify' was here
>  sound/oss/dmasound/dmasound_awacs.c: In function 'awacs_sleep_notify':
>  sound/oss/dmasound/dmasound_awacs.c:1428: error: 'PBOOK_SLEEP_NOW' undeclared (first use in this function)

Could you send the .config please?
-
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/