public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: venumadhav <venumadhav.josyula@wipro.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Compiling ecos with ARM Development suite or real view 	compiler tools.
Date: Thu, 03 Apr 2008 06:51:00 -0000	[thread overview]
Message-ID: <20080403065105.GK9320@lunn.ch> (raw)
In-Reply-To: <16466114.post@talk.nabble.com>

On Wed, Apr 02, 2008 at 11:47:23PM -0700, venumadhav wrote:
> 
> Hi Folks,
>  
> Has anybody attempted build ecos with ARM Developer suite now or in the
> past. The reason I ask this is because I have following questions,
>  
> 1. Is it worth pursuing the effort or am I wasting my time ?
> 2. Why is it so that we cannot compile ecos with armcc ?
> 3. Has anybody attempted this exercise now or in the past ?

See the recent thread about constructor prioritisation.....

In general, i would say you are wasting your time. eCos uses gcc
extensions, which i doubt armcc supports. I know people have attempted
this before, but i don't remember anybody reporting success.

     Andrew

-- 
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:[~2008-04-03  6:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03  6:47 venumadhav
2008-04-03  6:51 ` Andrew Lunn [this message]
     [not found]   ` <CBE0A8E1D067704EA75C8D910F98B93D02275FF9@HYD-MKD-MBX01.wipro.com>
2008-04-03  7:20     ` [ECOS] Compiling ecos with ARM Development suite or real viewcompiler tools Andrew Lunn
2008-04-03  9:24 ` [ECOS] Compiling ecos with ARM Development suite or real view compiler tools venumadhav

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=20080403065105.GK9320@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=venumadhav.josyula@wipro.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).