public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Narayana, Venkat A." <NarayVA@nsc-msg01.network.com>
To: "'Jonathan Larmour'" <jlarmour@redhat.com>,
	"Narayana, Venkat A." <NarayVA@nsc-msg01.network.com>
Cc: "'ecos-discuss@sourceware.cygnus.com'"
	<ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] Help! on building ecosconfigure
Date: Wed, 18 Apr 2001 10:48:00 -0000	[thread overview]
Message-ID: <A7E1C26945C8D211ADBF0008C709661A02A487D9@nsc-msg02.network.com> (raw)

Hi,
I can do that,but it takes away the fun;-).
Moreover, i think that ecosconfig tool has something to do with
cross-compilation.I reasoned that on the basis of input parameters
that we pass to configure script.I went thru the 'ecos Getting started'
manual and Redboot User's guide, but i didn't find any examples of making
ecosconfigure tool.
So, if i need to build Redboot ROM startup for ARM arch, then, since i use
ecosconfig tool( page 23 of Redboot users guide), then shouldn't i compile
ecosconfig to take care of cross-compilation? i guessing here.

Venkat


"Narayana, Venkat A." wrote:
> 
> Hi all,
> I have downloaded the ecos sources from cvs/redhat site.
> In the 'host' directory, i followed README and ran ' configure script'.
> What values i should give for 'build, host and target'?

The host directory is only relevant if you are building the host tools,
like ecosconfig. But you can download prebuilts for Windows and Linux from
http://sources.redhat.com/ecos/anoncvs.html

> I want to make
> redboot for RAM startup
> for XScale arch. what documents are relevant ?

The RedBoot user's guide. Go to http://sources.redhat.com/redboot/

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

             reply	other threads:[~2001-04-18 10:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 10:48 Narayana, Venkat A. [this message]
2001-04-18 10:56 ` Jonathan Larmour
  -- strict thread matches above, loose matches on Subject: below --
2001-04-19 14:32 Narayana, Venkat A.
2001-04-19 12:16 Narayana, Venkat A.
2001-04-19 12:33 ` Gary Thomas
2001-04-19 12:39   ` Jonathan Larmour
2001-04-19 12:35 ` Jonathan Larmour
2001-04-19 12:40 ` Mark Salter
2001-04-19 12:51   ` Jonathan Larmour
2001-04-19 13:03     ` Lewin A.R.W. Edwards
2001-04-19 13:56       ` Jonathan Larmour
2001-04-19 14:04         ` Lewin A.R.W. Edwards
2001-04-19 11:09 Narayana, Venkat A.
2001-04-19 11:47 ` Gary Thomas
2001-04-18 11:18 Narayana, Venkat A.
2001-04-18 11:30 ` Jonathan Larmour
2001-04-18 10:27 Narayana, Venkat A.
2001-04-18 10:32 ` Jonathan Larmour

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=A7E1C26945C8D211ADBF0008C709661A02A487D9@nsc-msg02.network.com \
    --to=narayva@nsc-msg01.network.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@redhat.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).