From: "Jayachandran C." <jayachandranc@netlogicmicro.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, binutils@sourceware.org
Subject: Re: XLR Linux/MIPS kernel build error
Date: Tue, 21 Jun 2011 22:26:30 +0530 [thread overview]
Message-ID: <20110621165628.GA5769@jayachandranc.netlogicmicro.com> (raw)
In-Reply-To: <20110621144340.GA11931@linux-mips.org>
On Tue, Jun 21, 2011 at 03:43:40PM +0100, Ralf Baechle wrote:
> I'm getting a build error with gcc 4.6.0 and binutils 2.21:
>
> [...]
> AS arch/mips/kernel/entry.o
> AS arch/mips/kernel/genex.o
> /home/ralf/src/linux/upstream-linus/arch/mips/kernel/genex.S: Assembler messages:
> /home/ralf/src/linux/upstream-linus/arch/mips/kernel/genex.S:524: Internal error!
> Assertion failure in append_insn at ../../gas/config/tc-mips.c line 2867.
> Please report this bug.
> make[4]: *** [arch/mips/kernel/genex.o] Error 1
> make[3]: *** [arch/mips/kernel] Error 2
> make[2]: *** [arch/mips] Error 2
> make[1]: *** [sub-make] Error 2
> make: *** [all] Error 2
> make: Leaving directory `/home/ralf/src/linux/obj/nlm_xlr-build'
>
> Not sure what's blowin up there and I haven't had a chance to try other
> binutils versions yet. Is this something known? None of the other MIPS
> kernel defconfigs is encountering this issue.
I have not used this GCC/binutils combination yet. But I have had success with the
code sourcery toolchain (needs minor patch to add -march=xlr cflags):
gcc version 4.5.2 (Sourcery G++ Lite 2011.03-53)
GNU ld (Sourcery G++ Lite 2011.03-53) 2.20.51.20100809
JC.
prev parent reply other threads:[~2011-06-21 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 14:43 XLR Linux/MIPS kernel build error Ralf Baechle
2011-06-21 15:05 ` Nick Clifton
2011-06-21 16:38 ` Ralf Baechle
2011-06-21 16:56 ` Jayachandran C. [this message]
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=20110621165628.GA5769@jayachandranc.netlogicmicro.com \
--to=jayachandranc@netlogicmicro.com \
--cc=binutils@sourceware.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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