From: Bart Veer <bartv@cygnus.co.uk>
To: brendan@dgs.monash.edu.au
Cc: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Re: compiler builds.
Date: Wed, 18 Aug 1999 08:23:00 -0000 [thread overview]
Message-ID: <199908181523.QAA29125@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <37B9FAFC.2AE6765@dgs.monash.edu.au>
>>>>> "Brendan" == Brendan Simon <brendan@dgs.monash.edu.au> writes:
Brendan> I was reading the document and it says to download the
Brendan> ecos software tools and to compile them. I already have
Brendan> built an egcs-1.1.2 cross-compiler that targets
Brendan> powerpc-eabi. Can I use this. I don't see any reasons why
Brendan> not. Extra libraries and startup code for board support
Brendan> packages can be placed in appropriate directories. Please
Brendan> advise on whether I MUST use the eCos compilers (gcc
Brendan> variants I assume).
Brendan> I'd like to use Insight as my debugger. I am in the
Brendan> process of building this for a powerpc-eabi target and
Brendan> can see no reasons why this should not work. Any
Brendan> comments?
In theory it should be possible to take the various toolchain
components from the sourceware site and combine them to get a set of
tools usable with eCos. The main components are gcc 2.95 (not any
earlier releases), gdb 4.18, and binutils. It should be possible to
add Insight to that list as well.
In practice there are no guarantees that this will work. gcc, gdb etc.
are all separate projects undergoing rapid development, and we do not
continually test all of the toolchain components for eCos
compatibility. The toolchain download that is available via the eCos
web pages has been specifically tested for eCos and is known to work.
So if people want a solid and tested toolchain than the eCos one is
appropriate. If you want the very latest compiler optimizations etc.
then feel free to try out the latest releases of everything. It is
possible that everything will just work for any given target. It is
also possible that there may be a few problems that you will need to
sort out.
Bart Veer // eCos net maintainer
prev parent reply other threads:[~1999-08-18 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-17 17:14 [ECOS] ECOS: " Brendan Simon
1999-08-18 7:38 ` Jonathan Larmour
1999-08-18 7:59 ` Dan Hovang
1999-08-18 8:23 ` Bart Veer [this message]
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=199908181523.QAA29125@sheesh.cygnus.co.uk \
--to=bartv@cygnus.co.uk \
--cc=brendan@dgs.monash.edu.au \
--cc=ecos-discuss@sourceware.cygnus.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).