public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Alessandro Pinto" <apinto@parades.rm.cnr.it>
To: "Jonathan Larmour" <jlarmour@redhat.co.uk>
Cc: <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] Re: Configuration tool problem
Date: Thu, 01 Jun 2000 08:57:00 -0000	[thread overview]
Message-ID: <01ce01bfcbe2$7cf0b360$2b259296@parades.rm.cnr.it> (raw)
In-Reply-To: <39367B5B.76DE437A@redhat.co.uk>

The ecos build now is OK and I tried to compile some file automatic
generated by VCC and all is OK.

But I'm brave and I'm thinking to use an ARM instuction set simulator. This
simulator need the RTOS library but the ones generated by the configuration
tool (libtarget.a) doesn't work.
There is the possibilities to compile the library for another compiler (in
this case armcc by arm) ?

THANKS

AP
------------------------------------------------------------------
Alessandro Pinto
Mobile: (+39)(0)3395366531
Address: Via L. Viani, 12
00125 Roma, Italy
http://web.tiscalinet.it/alessandro_pinto/index.htm
------------------------------------------------------------------


  reply	other threads:[~2000-06-01  8:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-29 18:27 [ECOS] about timeslice and same priority thread switch yyl
2000-05-30 14:47 ` Jonathan Larmour
2000-05-30 18:40   ` yyl
2000-05-31 13:13     ` Jonathan Larmour
2000-06-01  3:02       ` [ECOS] Configuration tool problem Alessandro Pinto
2000-06-01  8:03         ` [ECOS] " Jonathan Larmour
2000-06-01  8:57           ` Alessandro Pinto [this message]
2000-06-01  9:08             ` Jonathan Larmour
2000-06-01 22:31       ` [ECOS] about timeslice and same priority thread switch zhang
2000-06-02 11:12         ` Jonathan Larmour
     [not found] <3.0.5.32.20000601192104.00a1e630@mailhost>
2000-06-01 10:47 ` [ECOS] Re: Configuration tool problem Alessandro Pinto
2000-06-01 12:37 ` 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='01ce01bfcbe2$7cf0b360$2b259296@parades.rm.cnr.it' \
    --to=apinto@parades.rm.cnr.it \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@redhat.co.uk \
    /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).