From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Jan Dittmer" <jdi@l4x.org>
Cc: bryan.wu@analog.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Blackfin arch fixes (try #2)
Date: Thu, 12 Jul 2007 17:02:54 -0400 [thread overview]
Message-ID: <8bd0f97a0707121402sf1efc17nabb89e40c3e82095@mail.gmail.com> (raw)
In-Reply-To: <468DF478.1080403@l4x.org>
On 7/6/07, Jan Dittmer <jdi@l4x.org> wrote:
> Mike Frysinger wrote:
> > On 7/4/07, Jan Dittmer <jdi@l4x.org> wrote:
> >> Mike Frysinger wrote:
> >> > On 7/3/07, Jan Dittmer <jdi@l4x.org> wrote:
> >> >> Bryan Wu wrote:
> >> >>> Jie's patch is required because we will release our new Blackfin
> >> toolchain.
> >> >> So, what is the new toolchain version?
> >> >> gcc 4.1.1 (adi 07r1) / binutils 2.17 doesn't seem to work anymore:
> >> >
> >> > we'll post new toolchain binaries in a bit
> >>
> >> Hrm, somehow I don't understand it. On [1] you're
> >> talking about gcc 4.1.2 and binutils 2.17 supporting
> >> the -mcpu switch. But if you download the 2007R1 RC9
> >> toolchain from the Files section of the site (tar.gz)
> >> you actually get 4.1.1 without mcpu support. But the
> >> version string from gcc indicates 07r1.
> >> Care to explain?
> >
> > the syntax of the -mcpu option was extended
>
> But the tar-ball does _not_ contain 4.1.2
the version is irrelevant ... the syntax was extended and backported to 4.1.1
i put together nightly snapshots which you can find here:
http://blackfin.uclinux.org/gf/project/toolchain/frs/?action=index
-mike
next prev parent reply other threads:[~2007-07-12 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 0:37 Bryan Wu
2007-07-03 13:58 ` Jan Dittmer
2007-07-03 17:55 ` Mike Frysinger
2007-07-04 20:38 ` Jan Dittmer
2007-07-06 7:22 ` Mike Frysinger
2007-07-06 7:51 ` Jan Dittmer
2007-07-12 21:02 ` Mike Frysinger [this message]
2007-07-10 18:44 ` Jan Dittmer
2007-07-10 21:42 ` Robin Getz
2007-07-11 2:09 ` Bryan Wu
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=8bd0f97a0707121402sf1efc17nabb89e40c3e82095@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=bryan.wu@analog.com \
--cc=jdi@l4x.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®