From: Gary Thomas <gary@mlbassoc.com>
To: Raja Mallik <raja.mallik@moschip.com>
Cc: "Bhatia, Deepak" <Deepak.Bhatia@patni.com>,
eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] eCos Porting to SPARC V8 Architecture
Date: Fri, 06 May 2005 10:45:00 -0000 [thread overview]
Message-ID: <1115376341.5511.214.camel@hermes> (raw)
In-Reply-To: <1115376244.1630.8.camel@mazda>
On Fri, 2005-05-06 at 16:14 +0530, Raja Mallik wrote:
> http://kegel.com/crosstool/#download
>
> - you might as well try and build one on your won..
> - this is very good for any platform..
>
While I agree that Dan's tool is very useful, one needs to be careful as
crosstool is mostly setup for generating Linux tool chains. In general,
these are not what we use with eCos - make sure you are building the
appropriate embedded (ABI) tools.
> -raja
>
>
> On Fri, 2005-05-06 at 16:06, Bhatia, Deepak wrote:
> > Hello,
> >
> > Please help me in understanding whether GNU C/C++ Compilers are good for the
> > SPARC V8 Architecture based CPUs.
> >
> > Regards
> >
> > Deepak Bhatia
> > Software Consultant
> > Patni Computer Systems Limited
> > Mobile: 91 98111 96957
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
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:[~2005-05-06 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 10:36 Bhatia, Deepak
2005-05-06 10:42 ` Raja Mallik
2005-05-06 10:45 ` Gary Thomas [this message]
2005-05-06 11:02 Raghu
2005-05-06 11:06 ` Gary Thomas
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=1115376341.5511.214.camel@hermes \
--to=gary@mlbassoc.com \
--cc=Deepak.Bhatia@patni.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=raja.mallik@moschip.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).