From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Russell King <rmk@arm.linux.org.uk>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mike Frysinger <vapier.adi@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: linux-next: arm build failures
Date: Wed, 17 Jun 2009 23:08:04 +1000 [thread overview]
Message-ID: <20090617230804.5e353ec9.sfr@canb.auug.org.au> (raw)
In-Reply-To: <tnx3a9ztg14.fsf@pc1117.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
Hi Catalin,
On Wed, 17 Jun 2009 09:34:31 +0100 Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Over the past few days, I have started getting some arm configs (at least
> > iop13xx_defconfig and integrator_defconfig, but some others) failing to
> > build getting this error:
> >
> > SYSMAP System.map
> > SYSMAP .tmp_System.map
> > Inconsistent kallsyms data
> > Try setting CONFIG_KALLSYMS_EXTRA_PASS
> >
> > Is this something you have seen? Could it be my toolchain (I am
> > currently using gcc 4.4.0 and have not changed it recently)?
>
> I reported an error with kallsysms on ARM this Monday leading to
> inconsistent data:
>
> http://lkml.org/lkml/2009/6/15/233
>
> Could it be related?
Could be. I have added the proposed fix patch to my fixes tree until
Linus or Sam gets around to including it.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-06-17 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 6:26 linux-next: arm build failures Stephen Rothwell
2009-06-17 8:34 ` Catalin Marinas
2009-06-17 13:08 ` Stephen Rothwell [this message]
2009-06-19 15:13 ` Russell King
2009-06-20 5:54 ` [PATCH] Kallsyms problems (was: Re: linux-next: arm build failures) Stephen Rothwell
2009-06-20 12:41 ` Sam Ravnborg
2009-06-20 14:14 ` Russell King
2009-06-20 23:58 ` Stephen Rothwell
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=20090617230804.5e353ec9.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=sam@ravnborg.org \
--cc=vapier.adi@gmail.com \
/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