From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] toolchain: add Coldfire external toolchain from Sourcery CodeBench
Date: Wed, 18 Apr 2012 10:25:31 +0200 [thread overview]
Message-ID: <20120418102531.5b4d8425@skate> (raw)
In-Reply-To: <201204180054.35908.arnout@mind.be>
Le Wed, 18 Apr 2012 00:54:35 +0200,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> On Tuesday 10 April 2012 18:10:46 Thomas Petazzoni wrote:
> > +TOOLCHAIN_EXTERNAL_SITE=???
>
> Shouldn't that be
> http://sourcery.mentor.com/sgpp/lite/coldfire/portal/package9494/public/m68k-uclinux/
Yes, sorry. I implemented this during a week-end, and I had no Internet
connection at that time :)
I'll fix up and resend.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-04-18 8:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 16:10 [Buildroot] [RFC] Development around Coldfire Thomas Petazzoni
2012-04-10 16:10 ` [Buildroot] [PATCH 1/5] arch: re-enable m68k and add a few architecture variants Thomas Petazzoni
2012-04-10 16:10 ` [Buildroot] [PATCH 2/5] toolchain: add Coldfire external toolchain from Sourcery CodeBench Thomas Petazzoni
2012-04-17 22:54 ` Arnout Vandecappelle
2012-04-18 8:25 ` Thomas Petazzoni [this message]
2012-04-10 16:10 ` [Buildroot] [PATCH 3/5] toolchain: add m68k to the list of arch that can work without MMU Thomas Petazzoni
2012-04-10 17:28 ` Gustavo Zacarias
2012-04-10 16:10 ` [Buildroot] [PATCH 4/5] busybox: enable useful hush suboptions Thomas Petazzoni
2012-04-10 16:10 ` [Buildroot] [PATCH 5/5] board: add support for Coldfire MCF5208EVB board emulated by Qemu Thomas Petazzoni
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=20120418102531.5b4d8425@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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