From: "Strong Qu" <strong.qu@amd.com>
To: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] gcc install for ecos fails
Date: Mon, 12 Mar 2007 15:48:00 -0000 [thread overview]
Message-ID: <5A15D86EDE7573448683D46FC9FC8DD60129F2A3@torcaexmb4.atitech.com> (raw)
In-Reply-To: <45F56F62.6080900@zylin.com>
As I know the error is related to Cygwin. If you are not using big
endian platform you can use the already built binary package from eCos
website. You still use latest package by using CVS. Otherwise you need
some effort to workaround the problem.
-QuYQ
> -----Original Message-----
> From: ecos-discuss-owner@ecos.sourceware.org
> [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of
> Edgar Grimberg
> Sent: Monday, March 12, 2007 11:19 AM
> To: Morduch
> Cc: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] gcc install for ecos fails
>
> Morduch wrote:
> > Edgar,
> > I see different versions of gcc etc' in
> > http://www.zylin.com/libstdc++.html
> > than the http://ecos.sourceware.org/
> > is this the package recomended for use?
> >
> Hi Morduch,
>
> I've been using these packages for at least a couple of
> years. There are some binaries on the page, also, if you want
> to avoid the compiling process. Why don't you give it a try,
> run some of the standard eCos tests on the target and see if
> they work?
>
> Edgar
>
> --
> Before posting, please read the FAQ:
> http://ecos.sourceware.org/fom/ecos
> and search the list archive:
> http://ecos.sourceware.org/ml/ecos-discuss
>
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-03-12 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 13:06 Morduch
2007-03-12 13:33 ` Edgar Grimberg
2007-03-12 15:12 ` Morduch
2007-03-12 15:20 ` Edgar Grimberg
2007-03-12 15:48 ` Strong Qu [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=5A15D86EDE7573448683D46FC9FC8DD60129F2A3@torcaexmb4.atitech.com \
--to=strong.qu@amd.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).