This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Installation problems - ECOS toolset on Windows platform
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Andy Voelkel <andy at bushtaxi dot com>
- Cc: 'David Brennan' <eCos at brennanhome dot com>,eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 31 May 2005 13:37:25 -0600
- Subject: RE: [ECOS] Installation problems - ECOS toolset on Windows platform
- References: <200505311422286.SM01264@LatiDroid>
On Tue, 2005-05-31 at 12:19 -0700, Andy Voelkel wrote:
> >>So, I thought I'd try invoking the configuration tool from a bash shell. I
> >>negotiated my way to the directory containing the executable, and invoked
> >>it. This time the graphic interface came up, spewed a bunch of text into
> >its
> >>output window, and closed itself. As best I can tell, many of the error
> >>messages contained the string "this package does not have any valid
> >version
> >>subdirectories".
> >>
> >Did you set ECOS_REPOSITORY? Within whatever your basic installation
> >directory (/opt/ecos) you should have a shell script ecosenv.sh (or
> >ecosenv.csh). I recommend you run that after starting your bash shell.
>
> Unfortunately, running these files does not help. I have verified that the
> environment is being properly modified by issuing a "set | grep ECOS"
> command. Interestingly, I accidentally set this variable to the tools/bin
> directory at one point, and got a different error message from
> configtool.exe when I tried to run it. It said "tools/bin does not seem to
> be a repository". It then allowed me to browse to the actual packages folder
> (c:\progs\cygwin\opt\ecos\ecos-2.0\packages on my machine) When I selected
> this directory, I got the same old barrage of error messages about the lack
> of valid version subdirectories, and then configtool.exe quit.
Exactly what do you have ECOS_REPOSITORY set to? Perhaps you used
"abc\def" instead of "abc/def"?
Also, the scripts 'ecosenv.sh' are not run, but rather included, like
this:
% . ecosenv.sh
This way, the script can set environment variables which persist in the
calling shell.
>
> This makes me suspect that for in fact my packages directory does not in
> fact "have any valid version subdirectories". I don't understand this
> because it is a fresh ECOS install right off the internet, and at this stage
> in the learning curve I'm not even sure I understand the error messages. And
> why does configtool quit after issuing them.
>
> Can anyone help with this? I'm getting tired of dorking around and not even
> being able to run the most basic stuff.
>
> BTW, I can't find any meaningful references on the importance of using the
> ECOS_REPOSITORY variable when using configtool.exe anywhere in the
> documentation I downloaded. And the mailing list FAQ on Windows installation
> issues seems to be empty. Should I write up an installation FAQ once these
> issues are resolved?
>
> - Andy Voelkel
>
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss