public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Harsha D" <harshad@sanyo.co.in>
To: "Gary Thomas" <gary@mlbassoc.com>, "Andrew Lunn" <andrew@lunn.ch>
Cc: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] which gcc toolchain to use ?
Date: Wed, 27 Jul 2005 03:22:00 -0000	[thread overview]
Message-ID: <C03A3C267DDF184EA523BBAB577BF92405B170@blrexsr1.slti.sanyo.co.in> (raw)


Gary,

As i said earlier ... my redboot hangs in do_version.  (at the place
where the RAM range is printed).
I thought may be optimization flag was playing around..(as was in the
case of v4.0).  So just tried 
removing it.

Even then how can optimization flag effect the working of redboot as a
whole ? 


Andrew, 

I just went around looking for the toolchain and i came across this "
... some problems with gnu 
tools on cygwin... ecos on cygwin is not supported... "

And Now i have this doubt "Development on cygwin?" or "Development on
linux?".  Although i am 
more comfortable working on windows, i would definitely like to avoid
extra work needed (if its 
the case) to make it work using cygwin.


regards
hasha


-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com]
Sent: 26 July 2005 18:36
To: Andrew Lunn
Cc: Harsha D; eCos Discussion
Subject: Re: [ECOS] which gcc toolchain to use ?


On Tue, 2005-07-26 at 11:48 +0200, Andrew Lunn wrote:
> On Tue, Jul 26, 2005 at 02:54:57PM +0530, Harsha D wrote:
> > Hi
> > 
> > I have been trying to port ecos on ARM9 based board.
> > I tried with gcc v4.0 (cygwin) and gcc v3.4.3
> > 
> > 
> > In my case i have observed that
> > 
> > in v4.0 > 
> > 	Removing optimization(O2) flag... redboot works
> > 	Including optimization flag... redboot fails 
> > 
> > in v3.4.2	>
> > 	Removing optimization flag... redboot FAILS
> > 	Including optimization flag... redboot works
> > 
> > 
> > also....redboot seems to hang at do_version, printing the RAM range.
> > 
> > 
> > I would like to know which is the best/suitable gcc toolchain to be
used
> > with eCos
> 
> See:
> 
> http://ecos.sourceware.org/getstart.html
> 
> Get the toolchains from there. They are known to work well.

I've also had good luck with 3.4.3.  However, I never build
without optimization (why would you want to?)

-- 
------------------------------------------------------------
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

             reply	other threads:[~2005-07-27  3:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27  3:22 Harsha D [this message]
2005-07-27  7:16 ` Andrew Lunn
2005-07-27 10:55   ` [ECOS] "Fis init" failed on EB40A Jaws
2005-07-27 11:18     ` [ECOS] " Jani Monoses
2005-07-27 11:35       ` Domenico La Fauci
2005-07-27 11:39         ` Jani Monoses
2005-07-27 12:09           ` Domenico La Fauci
2005-07-27 12:57     ` [ECOS] " Dirk Eibach
2005-07-27 16:50       ` Jaws
2005-07-27 16:56         ` Gary Thomas
2005-07-27 17:06     ` Paul D. DeRocco
2005-07-28 15:22       ` Domenico La Fauci
2005-07-28 15:36         ` Andrew Lunn
2005-07-28 15:54           ` Jaws
  -- strict thread matches above, loose matches on Subject: below --
2005-07-26  9:21 [ECOS] which gcc toolchain to use ? Harsha D
2005-07-26  9:49 ` Andrew Lunn
2005-07-26 13: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=C03A3C267DDF184EA523BBAB577BF92405B170@blrexsr1.slti.sanyo.co.in \
    --to=harshad@sanyo.co.in \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.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).