From: Warren Jasper <warrenj@tx.ncsu.edu>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] version of gcc for NEC MIPS VR4300
Date: Tue, 24 Apr 2001 09:03:00 -0000 [thread overview]
Message-ID: <3AE5A2CB.F32F9E58@tx.ncsu.edu> (raw)
--
The documentation for
"Building the NEC MIPS VR4300 development tools for Windows"
(an the one for Linux for that matter) states:
The GNU Compiler Collection web site contains plenty of information
about installing and using
GCC. Unfortunately the most recent official release (GCC 2.95.2) is not
capable of supporting eCos
for NEC MIPS VR4300. A snapshot of the GCC development sources should be
used to obtain the
most up-to-date compiler with new features and bug fixes.
eCos has been tested with the 2000-03-13 snapshot, but it is likely that
later snapshots will fix bugs
that have not yet been discovered. If you have compiler problems you may
wish to consider updating
to a more recent snapshot, or reverting to an older one.
Unfortunatley, I could not find the 2000-03-13 snapshot.
Has anybody used a more recent snapshot (like dated 2001) that you
know works for the MIPS VR4300? Please email to me, as I am
not on the list.
Thanks,
-- Warren
Warren J. Jasper
wjasper@tx.ncsu.edu
reply other threads:[~2001-04-24 9:03 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=3AE5A2CB.F32F9E58@tx.ncsu.edu \
--to=warrenj@tx.ncsu.edu \
--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).