From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: di yan <diyan1@yahoo.com>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] new ecosconfig tool
Date: Sun, 18 Feb 2001 06:06:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20010218090130.00b45c00@larwe.com> (raw)
In-Reply-To: <20010218055432.12650.qmail@web5201.mail.yahoo.com>
Hello Di,
>1. check out ecos 1.3.1.
>2. update ecos to current.
>3. using new ecosconfig tool(download from anonycvs)
>in Linux platform.
>ecosconfig list
I don't get those errors. Maybe it is something odd/different about
_updating_ rather than _checking out latest_. Try just cd /opt and checkout
latest eCos sources. You'll end up with a directory "/opt/ecos", set
ECOS_REPOSITORY=/opt/ecos/packages and try again "ecosconfig list".
I currently have both eCos 1.3.1 and current CVS sources on my development
system. I have replaced ecos-1.3.1/tools/bin/ecosconfig with the latest
version, so my PATH is constant at
/tools/H-i686-pc-linux-gnu/bin:/opt/ecos-1.3.1/tools/bin and I simply
change ECOS_REPOSITORY when switching between versions.
=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/
"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."
next prev parent reply other threads:[~2001-02-18 6:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-17 21:54 di yan
2001-02-18 6:06 ` Lewin A.R.W. Edwards [this message]
2001-02-19 6:29 ` Bart Veer
2001-02-19 6:33 ` Lewin A.R.W. Edwards
2001-02-19 6:53 ` [ECOS] Still having problems getting networking up Bart Veer
2001-02-19 22:13 ` [ECOS] new ecosconfig tool di yan
2001-02-23 9:47 ` Jonathan Larmour
2001-02-19 13:32 ` [ECOS] USB host mode support? Tim Michals
2001-02-20 5:26 ` Bart Veer
2001-02-20 5:32 ` Tim Michals
2001-02-20 5:54 ` Lewin A.R.W. Edwards
2001-02-20 6:17 ` Tim Michals
2001-02-20 7:10 ` Andrew Lunn
2001-02-20 7:41 ` Lewin A.R.W. Edwards
2001-02-20 9:50 ` Tim Michals
2001-02-20 10:11 ` Lewin A.R.W. Edwards
2001-02-21 6:42 ` Bart Veer
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=4.3.2.7.2.20010218090130.00b45c00@larwe.com \
--to=larwe@larwe.com \
--cc=diyan1@yahoo.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).