From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] configtool 1.3.1.2 not working?
Date: Tue, 06 Feb 2001 09:45:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20010206123836.00ac3c10@larwe.com> (raw)
In-Reply-To: <3A803656.45B62DE2@redhat.com>
Hello Jonathan,
> > from within the config tool. The application just hangs when I select Build
> > - Library (no errors).
>
>All I can say is that it works for me :-/. Is this Windows 95/98?
NTWS 4, P2-400, 128Mb RAM. I just tried it on my own 98 workstation, and it
does the same thing. I thought it might have just been thinking (no
noticeable disk access), but I left it for 10 minutes and it still didn't
do anything. Is it worth me installing Win2k on a machine here to test it,
do you think?
[Are you beginning to believe me when I say that I am infested by personal
demons? ;)]
Anyhow, is it possible to use the command-line tools under Windows? If I
use the graphical tool to create my .ecc then run ecosconfig tree (after
setting repository correctly), it doesn't work; I get an error for every
single package saying that there isn't a valid version directory for it.
(thinks: WHOA! Maybe that is what is happening in the background and making
the graphical tool seem to hang. I've tried these new configtool/ecosconfig
both on the latest CVS and 1.3.1 trees, and the same result. I went back to
the old 1.3.1 Win tools for the moment).
=== 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."
prev parent reply other threads:[~2001-02-06 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 8:23 Lewin A.R.W. Edwards
2001-02-06 9:37 ` Jonathan Larmour
2001-02-06 9:45 ` Lewin A.R.W. Edwards [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=4.3.2.7.2.20010206123836.00ac3c10@larwe.com \
--to=larwe@larwe.com \
--cc=ecos-discuss@sources.redhat.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).