From: Andrew Lunn <andrew@lunn.ch>
To: Richard Rauch <Richard.Rauch@vipa.de>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] any experiences with arm gcc 3.4.1 and ecos ?
Date: Mon, 02 Aug 2004 12:48:00 -0000 [thread overview]
Message-ID: <20040802124846.GH14248@lunn.ch> (raw)
In-Reply-To: <000e01c47886$1346e2e0$408010ac@leo>
On Mon, Aug 02, 2004 at 01:44:30PM +0200, Richard Rauch wrote:
> Then I'm doing something wrong with my toolchain.
> I reloaded now eCos from internet again ( sh ecos-install.tcl),
That will just pull eCos 2.0 which is over a year old. Take a look at
http://ecos.sourceware.org/anoncvs.html
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2004-08-02 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 8:58 Neundorf, Alexander
2004-07-30 7:48 ` fredrik
2004-07-30 12:42 ` Richard Rauch
2004-07-30 12:50 ` [ECOS] Linker Problem eCos 2.0 and gcc 3.4.1 (arm-elf) Richard Rauch
2004-08-02 10:16 ` [ECOS] any experiences with arm gcc 3.4.1 and ecos ? Andrew Lunn
2004-08-02 11:45 ` Richard Rauch
2004-08-02 12:48 ` Andrew Lunn [this message]
2004-08-02 15:49 ` Richard Rauch
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=20040802124846.GH14248@lunn.ch \
--to=andrew@lunn.ch \
--cc=Richard.Rauch@vipa.de \
--cc=ecos-discuss@sources.redhat.com \
/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).