From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Robert Schwebel" <r.schwebel@pengutronix.de>
Cc: "Adrian Bunk" <bunk@kernel.org>,
hskinnemoen@atmel.com, linux-kernel@vger.kernel.org
Subject: Re: Working upstream toolchain for avr32?
Date: Fri, 14 Dec 2007 15:21:45 -0500 [thread overview]
Message-ID: <8bd0f97a0712141221o3a65a5efo40c19ab12f7078c6@mail.gmail.com> (raw)
In-Reply-To: <20071214200318.GM3851@pengutronix.de>
On Dec 14, 2007 3:03 PM, Robert Schwebel <r.schwebel@pengutronix.de> wrote:
> On Thu, Dec 13, 2007 at 08:56:17PM +0100, Adrian Bunk wrote:
> > AFAIK the latest available AVR32 toolchains are some patched gcc 4.0 and
> > some patched binutils 2.17, and avr32 is currently the only architecture
> > in the kernel where upstream of both of them is not capable of building
> > a kernel for the architecture.
>
> Is an upstream toolchain available which is able to build blackfin?
binutils -- yes
uClibc -- yes (for FLAT)
gcc -- yes and no
we have some pieces in gcc, but if you want an
up-to-date-tested-known-working combination, you can fetch
sources/binaries from:
http://blackfin.uclinux.org/gf/project/toolchain/frs
we're working now to make sure that when gcc-4.3 is branched/released,
we're part of it
-mike
next prev parent reply other threads:[~2007-12-14 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 19:56 Adrian Bunk
2007-12-14 9:41 ` Haavard Skinnemoen
2007-12-28 8:52 ` Adrian Bunk
2007-12-14 20:03 ` Robert Schwebel
2007-12-14 20:21 ` Mike Frysinger [this message]
2007-12-14 20:28 ` Robert Schwebel
2007-12-14 20:35 ` Mike Frysinger
2007-12-14 20:55 ` Robert Schwebel
2007-12-14 21:23 ` Mike Frysinger
2007-12-14 21:59 ` Robert Schwebel
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=8bd0f97a0712141221o3a65a5efo40c19ab12f7078c6@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=bunk@kernel.org \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=r.schwebel@pengutronix.de \
/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®