public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001176] Repository Error
Date: Mon, 21 Mar 2011 09:53:00 -0000	[thread overview]
Message-ID: <20110321095329.89A192F80006@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001176-13@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001176

--- Comment #4 from John Dallaway <john@dallaway.org.uk> 2011-03-21 09:53:27 GMT ---
(In reply to comment #3)

> Yes have attempted to install the eCosPro RTOS (version
> 2.0.102) and are seeing an error when i invoke the eCos Configuration Tool.
> 
> "Invalid repository directory" this is the message i am geting when tried to
> invoke the tool.
> 
> For version please find attached snap shot.
> 
> Yes this on Windows 7/ 32 bit.

First, make sure that the eCos Configuration Tool is set up to look for the
repository at C:\cygwin\opt\ecos\ecos-2.0.102 using the "Build -> Repository"
menu item. Note that you should omit the "\packages" directory when specifying
the repository path. Hopefully this will eliminate the "Invalid repository
directory" message.

However, your build of the eCos Configuration Tool precedes the eCos 3.0
release so you may discover other issues when using it with Windows Vista or
Windows 7. I would recommend using the latest snapshot build of the eCos
Configuration Tool instead:

  http://ecos.sourceware.org/ml/ecos-discuss/2011-02/msg00031.html

You _might_ also need a more recent Cygwin installation. Details for installing
Cygwin for use with eCos are at:

  http://ecos.sourceware.org/cygwin.html

Does this resolve the reported problem? Please confirm.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-03-21  9:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-1001176-13@http.bugs.ecos.sourceware.org/>
2011-03-21  8:01 ` bugzilla-daemon
2011-03-21  8:53 ` bugzilla-daemon
2011-03-21  9:53 ` bugzilla-daemon [this message]
2011-03-23 11:50 ` bugzilla-daemon
2011-03-23 13:23 ` bugzilla-daemon
2011-03-25 10:35 ` bugzilla-daemon
2011-03-29  4:17 ` bugzilla-daemon
2011-03-29  6:53 ` bugzilla-daemon
2011-03-29  7:28 ` bugzilla-daemon
2011-03-29  8:09 ` bugzilla-daemon
2011-03-31 11:31 ` bugzilla-daemon
     [not found] <bug-1001176-777@http.bugs.ecos.sourceware.org/>
2011-03-21  8:01 ` bugzilla-daemon
2011-03-21  8:53 ` bugzilla-daemon
2011-03-21  9:53 ` bugzilla-daemon
2011-03-23 11:50 ` bugzilla-daemon
2011-03-23 13:23 ` bugzilla-daemon
2011-03-25 10:35 ` bugzilla-daemon
2011-03-29  4:17 ` bugzilla-daemon
2011-03-29  6:53 ` bugzilla-daemon
2011-03-29  7:28 ` bugzilla-daemon
2011-03-29  8:09 ` bugzilla-daemon
2011-03-31 11:31 ` bugzilla-daemon
2016-02-29  5:18 ` bugzilla-daemon

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=20110321095329.89A192F80006@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-bugs@ecos.sourceware.org \
    /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).