From: Sam Ravnborg <sam@ravnborg.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: -git11 breaks parisc and sh even more
Date: Tue, 13 Sep 2005 20:57:59 +0200 [thread overview]
Message-ID: <20050913185759.GA17272@mars.ravnborg.org> (raw)
In-Reply-To: <20050913174754.GA13132@mipter.zuzino.mipt.ru>
Hi Alexey.
On Tue, Sep 13, 2005 at 09:47:54PM +0400, Alexey Dobriyan wrote:
> 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"
> ...
> -----------------------------------------------------------------------
I have tried to understand why this happens with no success..
Not much has changed in how we actually compile the .c -> .s files.
In both cases it looks like gcc is warning that a sane typedef is not
present.
Have you tried to dive more into this, or have you just reported the
breakage?
Sam
next prev parent reply other threads:[~2005-09-13 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 17:47 Alexey Dobriyan
2005-09-13 18:57 ` Sam Ravnborg [this message]
2005-09-13 20:37 ` Alexey Dobriyan
2005-09-13 20:39 ` Sam Ravnborg
2005-09-14 7:42 ` Grant Grundler
2005-09-14 7:43 ` Ingo Molnar
2005-09-14 7:44 ` Ingo Molnar
2005-09-14 9:17 ` Grant Grundler
2005-09-14 12:50 ` Matthew Wilcox
2005-09-14 14:52 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050913185759.GA17272@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®