From: jlarmour@cygnus.co.uk (Jonathan Larmour)
To: brendan@dgs.monash.edu.au
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] ECOS: compiler builds.
Date: Wed, 18 Aug 1999 07:38:00 -0000 [thread overview]
Message-ID: <199908181438.PAA12218@peshwari.cygnus.co.uk> (raw)
In-Reply-To: <37B9FAFC.2AE6765@dgs.monash.edu.au>
In article < 37B9FAFC.2AE6765@dgs.monash.edu.au > you write:
>
>I am contemplating using eCos on an embedded product using the MPC860
>processor. It has three processor boards. 1 board requires TCP/IP and
>SNMP as well as PCMCIA support. I don't think eCos can support these at
>the moment (please correct me if I am wrong)
It can't without commercial software from one of our partners, no.
>I was reading the document and it says to download the ecos software
>tools and to compile them. I already have built an egcs-1.1.2
>cross-compiler that targets powerpc-eabi. Can I use this. I don't see
>any reasons why not.
I'm 99% certain egcs-1.1.2 does not support constructor priority ordering
for powerpc-eabi. But you should be able to use either gcc-2.95 or the
eCos software tools we provide.
>I'd like to use Insight as my debugger. I am in the process of building
>this for a powerpc-eabi target and can see no reasons why this should
>not work. Any comments ?
We've used it happily here on both Windows and Unix, so there really
shouldn't be any problems.
Hope this helps,
Jifl
--
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK. Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
my brains kept falling out." || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/ These opinions are all my own fault
next prev parent reply other threads:[~1999-08-18 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-17 17:14 Brendan Simon
1999-08-18 7:38 ` Jonathan Larmour [this message]
1999-08-18 7:59 ` Dan Hovang
1999-08-18 8:23 ` [ECOS] " Bart Veer
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=199908181438.PAA12218@peshwari.cygnus.co.uk \
--to=jlarmour@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).