From: Jonathan Larmour <jlarmour@redhat.com>
To: peter_ku <peter_ku@issc.com.tw>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] GNU tools combination for eCos
Date: Mon, 20 May 2002 18:53:00 -0000 [thread overview]
Message-ID: <3CE9A88A.B7912FF3@redhat.com> (raw)
In-Reply-To: <000501c1fc1b$7b6f68e0$790114ac@issc.com.tw>
peter_ku wrote:
>
> Hi,
>
> My work environment is Window Me and the hw-target is E7T
> I use the following combination to generate eCos, according to the eCos web site.
> binutils 2.10.1
> GCC2.95.2 + ecos-gcc-2952.pat
> Insight 5.0 + insight-tcl.pat
>
> everything is fine, except that I can't run gdb (I can run gdb -nw). and I check the mail list.
> and understand that insight 5.0 have some problem running under win98.
>
> But I think maybe the insight 5.0 is too old to find the update version on the ftp site.
> So I download insight 5.1, but I fail to compile. maybe the GCC is too old , I think.
Perhaps Insight 5.1.1 or 5.2 would be better:
ftp://sources.redhat.com/pub/gdb/releases/
Note you won't need the insight-tcl.pat for these.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2002-05-21 1:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 7:24 peter_ku
2002-05-20 18:53 ` Jonathan Larmour [this message]
2002-05-20 20:31 ` [ECOS] E7T timer0 interrupt issue ? peter_ku
2002-05-20 20:56 ` Simoncc
2002-05-21 7:34 ` Gary Thomas
2002-05-22 8:22 ` peter_ku
2002-05-28 12:28 ` Jonathan Larmour
2002-05-20 20:41 ` [ECOS] GNU tools combination for eCos peter_ku
2002-05-21 7:44 ` Jonathan Larmour
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=3CE9A88A.B7912FF3@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=peter_ku@issc.com.tw \
/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).