public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: eCos discussion <ecos-discuss@sources.redhat.com>
Subject: [ECOS] [Fwd: ]
Date: Tue, 30 Jan 2001 05:07:00 -0000	[thread overview]
Message-ID: <3A76BCA0.C202E1C4@redhat.com> (raw)

 


To : ecos-discuss at redhat dot com
From : ra jeev <mail_jeev at usa dot net>
Date : 29 Jan 2001 22:44:29 MST

hi guys,
   we are able to compile ecos successfully with our cross-compiler for
   an ARM target. where does the compiler store the image of ecos so that    
we can convert that image into binary and run it on our multiICE kit?
   also when we compile our applications what will be the name of the
   executable, will it have a .axf extension?
   thanx a lot in advance.
   with regards
   rajeev

____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1

             reply	other threads:[~2001-01-30  5:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30  5:07 Jonathan Larmour [this message]
2001-01-31 23:23 ` Jonathan Larmour
     [not found] <fc5cbb32050628021420c2a779@mail.gmail.com>
2005-06-28 11:27 ` [ECOS] Fwd: Rohit Agarwal
2005-06-28 11:51   ` Andrew Lunn
     [not found] <rasyrb44.zus1w6nt.y50zz.hrkq@digitaldells.com>
2019-01-30  7:28 ` tayyaba azeem
     [not found] <auqzdnwc.wdvvtvfr.7secq.5f1c@sammitrauto.com>
2020-02-17 18:57 ` tayyaba azeem
     [not found] <dp5f9a4z.25wns5un.q3154.82ya@sammitrauto.com>
2020-02-17 18:57 ` tayyaba azeem
     [not found] <eb5v1ts1.anctw1h5.50804.k6er@bbraunconnect.co.in>
2020-03-04 21:31 ` tayyaba azeem
     [not found] <8xctmhsp.e9ez6v1u.153k3.crt7@bbraunconnect.co.in>
2020-03-04 21:31 ` tayyaba azeem

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=3A76BCA0.C202E1C4@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sources.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).