From: Jonathan Larmour <jlarmour@redhat.com>
To: Ron Avisa <ravisa@base2software.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Hello Example solution
Date: Thu, 02 Aug 2001 14:04:00 -0000 [thread overview]
Message-ID: <3B69C076.D1F99E2B@redhat.com> (raw)
In-Reply-To: <4.2.0.58.20010802135644.00949f00@128.121.113.105>
Ron Avisa wrote:
>
> Many thanks!
> I moved all the example files to
>
> /c/work/examples/
>
> and tried running them from there and they work perfectly.
> I'll go ahead and get the latest GDB snapshots as well.
Yeah, it would be useful if you tried it with a recent GDB so that I can
arrange to get it fixed if the problem is still there.
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
prev parent reply other threads:[~2001-08-02 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 16:21 [ECOS] Hello Example Ron Avisa
2001-08-01 20:16 ` Jonathan Larmour
2001-08-02 12:44 ` Ron Avisa
2001-08-02 13:00 ` Jonathan Larmour
2001-08-02 14:04 ` [ECOS] Hello Example solution Ron Avisa
2001-08-02 14:04 ` Jonathan Larmour [this message]
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=3B69C076.D1F99E2B@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=ravisa@base2software.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).