From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
John Reiser <jreiser@bitwagon.com>,
Wu Zhangjin <wuzhangjin@gmail.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ralf Baechle <ralf@linux-mips.org>,
Linus <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: ftrace/MIPS related x86_64 build failure on in Linus' tree
Date: Thu, 16 Dec 2010 09:00:19 +1100 [thread overview]
Message-ID: <20101216090019.639191a1.sfr@canb.auug.org.au> (raw)
In-Reply-To: <AANLkTimgNVUaQcRdva_usq1XX=vp1xwHM3rUeT_hNCZd@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
Hi Arnaud,
On Wed, 15 Dec 2010 01:45:45 -0500 Arnaud Lacombe <lacombar@gmail.com> wrote:
>
> On Wed, Dec 15, 2010 at 12:04 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Since October 31 our x86_64 allmodconfig builds have been failing like this:
> >
> > /opt/crosstool/gcc-4.4.3-nolibc/x86_64-linux/bin/x86_64-linux-ld: arch/x86/ia32/sys_ia32.o: bad reloc symbol index (0x1000000 >= 0x6b) for offset 0x808080 in section `__mcount_loc'
> > arch/x86/ia32/sys_ia32.o: could not read symbols: Bad value
> >
> I got the same on mips, target was BE, toolchain's host was LE.
> Doesn't https://lkml.org/lkml/2010/12/2/224 address the issue ? This
> patch does not seem to have reached Linus tree yet.
Thanks for pointing that out. I wonder how we can push that along.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-12-15 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 5:04 Stephen Rothwell
2010-12-15 6:45 ` Arnaud Lacombe
2010-12-15 22:00 ` Stephen Rothwell [this message]
2010-12-15 22:25 ` Steven Rostedt
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=20101216090019.639191a1.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=jreiser@bitwagon.com \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=wuzhangjin@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
all inboxes | Powered by JetHome®