From: Andrew Lunn <andrew@lunn.ch>
To: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: FWD: [ECOS] GCC 4.3.2 toolchains for arm, cortex, mips, powerpc
Date: Thu, 25 Sep 2008 07:29:00 -0000 [thread overview]
Message-ID: <20080925072818.GB19581@lunn.ch> (raw)
> ----- Forwarded message from ?yvind Harboe <oyvind.harboe@zylin.com> -----
>
> X-Spam-Status: No, score=-6.6 required=4.0 tests=BAYES_00,RCVD_IN_DNSWL_MED
> autolearn=ham version=3.2.5
> Date: Wed, 24 Sep 2008 11:49:02 +0200
> From: ?yvind Harboe <oyvind.harboe@zylin.com>
> To: eCos Disuss <ecos-discuss@ecos.sourceware.org>
> Subject: [ECOS] GCC 4.3.2 toolchains for arm, cortex, mips, powerpc
>
> I've been toying around with building GCC toolchains(as one does...).
>
> They are ready for testing if anyone is interested:
>
> http://mail.zylin.com/pipermail/zylin-discuss_zylin.com/2008-September/000557.html
>
> Feedback welcome!
Hi eCosCentric guys,
A new set of toolchains is on the plan for the 3.0 release. What is
the state of this? Would it be better to make them available ASAP and
try to redirect people to what will be the new official tools rather
than these tools oyvind has compiled?
Thanks
Andrew
reply other threads:[~2008-09-25 7:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080925072818.GB19581@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-maintainers@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).