-git11 breaks parisc and sh even more

From: Alexey Dobriyan
Date: Tue Sep 13 2005 - 12:38:22 EST


2.6.13-git10 was OK (read: allmodconfig still broken, but not _that_
early).

If anybody want to see full logs, they are at
ftp://ftp.berlios.de/pub/linux-sparse/logs/2.6.13-git11/W_sparse_{parisc,sh}.bz2
-----------------------------------------------------------------------
parisc:

2.6.13-git11
hppa-unknown-linux-gnu-gcc (GCC) 3.4.4 (Gentoo 3.4.4-r1)
which: no palo in ($PATH)
CHK include/linux/version.h
UPD include/linux/version.h
SYMLINK include/asm -> include/asm-parisc
which: no palo in ($PATH)
scripts/kconfig/conf -s arch/parisc/Kconfig
#
# using defaults found in .config
#
SPLIT include/linux/autoconf.h -> include/config/*
CC arch/parisc/kernel/asm-offsets.s
In file included from include/asm/spinlock.h:4,
from include/asm/bitops.h:5,
from include/linux/bitops.h:77,
from include/linux/thread_info.h:20,
from include/linux/spinlock.h:53,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from arch/parisc/kernel/asm-offsets.c:31:
include/asm/system.h:174: error: parse error before "pa_tlb_lock"
...
-----------------------------------------------------------------------
sh:

2.6.13-git11
sh-unknown-linux-gnu-gcc (GCC) 3.4.4 (Gentoo 3.4.4-r1)
CHK include/linux/version.h
UPD include/linux/version.h
Generating include/asm-sh/machtypes.h
SPLIT include/linux/autoconf.h -> include/config/*
SYMLINK include/asm-sh/cpu -> include/asm-sh/cpu-sh4
SYMLINK include/asm-sh/mach -> include/asm-sh/unknown
SYMLINK include/asm -> include/asm-sh
CC arch/sh/kernel/asm-offsets.s
In file included from include/linux/spinlock_types.h:13,
from include/linux/spinlock.h:80,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from include/linux/mm.h:4,
from arch/sh/kernel/asm-offsets.c:13:
include/asm/spinlock_types.h:16: error: parse error before "atomic_t"
...
-----------------------------------------------------------------------

-
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/