From: David Daney <david.daney@cavium.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"ralf@linux-mips.org" <ralf@linux-mips.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: linux-next: toolchain version for mips builds, esp. cavium
Date: Fri, 09 Mar 2012 14:44:34 -0800 [thread overview]
Message-ID: <4F5A87D2.5010100@cavium.com> (raw)
In-Reply-To: <CAP=VYLpk9RonUUWmnC2-7wPi7Oqra_y7K4qQNLfMYqNKMo8QMg@mail.gmail.com>
On 03/09/2012 02:01 PM, Paul Gortmaker wrote:
> Hi Stephen,
>
> The linux-next builds for cavium defconfig have been failing for
> quite some time now, since it tries to use gcc-4.2 and the option
> for the octeon didn't appear until gcc-4.4 ("-march=octeon")
>
> http://kisskb.ellerman.id.au/kisskb/target/5509/
>
> I'm not sure there is any real "best" choice (hence I cc'd David
> and Ralf) but I just tested by grabbing the toolchain from here:
As you note, The OCTEON kernel build currently requires -march=octeon,
this is not gratuitous. There is some asm code in there that requires
OCTEON support in the toolchain. So currently an attempt to use a
toolchain that doesn't support -march=octeon will fail.
So there are a couple of choices:
1) Use a modern toolchain.
2) Figure out how to patch the kernel such that a modern toolchain is
not needed.
I don't really plan on working on #2.
David Daney
>
> ftp://ftp.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.2/
>
> and it seems fine with building the cavium. I'm not sure if the
> kisskb does per-target toolchain, or needs it per-arch, but I would
> suspect that the above is fine for all of mips anyway.
>
> What is the process for getting a different toolchain building the
> cavium in linux-next?
>
> Thanks,
> Paul.
>
prev parent reply other threads:[~2012-03-09 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 22:01 linux-next: toolchain version for mips builds, esp. cavium Paul Gortmaker
2012-03-09 22:38 ` Stephen Rothwell
2012-03-09 22:44 ` David Daney [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=4F5A87D2.5010100@cavium.com \
--to=david.daney@cavium.com \
--cc=linux-next@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=ralf@linux-mips.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).