public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: spreet singh <spreetsingh@yahoo.com>
To: ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Fwd: Re: [ECOS] building ecos using configuration tools under windows - invalid data base
Date: Sat, 16 Jun 2007 00:19:00 -0000	[thread overview]
Message-ID: <264695.7453.qm@web62203.mail.re1.yahoo.com> (raw)


--- spreet singh <spreetsingh@yahoo.com> wrote:

> Date: Fri, 15 Jun 2007 11:40:44 -0700 (PDT)
> From: spreet singh <spreetsingh@yahoo.com>
> Subject: Re: [ECOS] building ecos using
> configuration tools under windows - invalid data
> base
> To: Mike Sweeney <msweeney77@gmail.com>
> 
> Thanks for the response.
> I tried the suggestion and it stll gives the same
> response:
> " Error opening eCos repository - Invalid package
> database"
> and other message is:
> ecos.db:error - couldnt read file
> "/ecoscvs/ecos/packages/ecos.db" no such file or
> directory.
> spreet
> 
> --- Mike Sweeney <msweeney77@gmail.com> wrote:
> 
> > On 6/15/07, spreet singh <spreetsingh@yahoo.com>
> > wrote:
> > > All,
> > >   I am trying to build ecos using configuration
> > tools
> > > based on the ecos from cvs.
> > >   I downloaded the configuration tool -
> 060710.exe
> > > extracted from eCos Configuration Tool Version 2
> > for
> > > windows (2006-07-10) from the net.
> > >   When I invoke configuration tool, it comes up
> > with
> > > the message:
> > >   " Error opening eCos repository - Invalid
> > package
> > > database"
> > >
> > >   Message on the configtool screen is: could not
> > read
> > > file "ecoscvs/ecos/packages/ecos.db"
> > >
> > >   Looking at the path
> > c:/cygwin/ecoscvs/ecos/packages,
> > > there is a file ecos.db
> > >
> > >   using the command line to query the
> > ECOS_REPOSITORY,
> > > it points to /ecoscvs/ecos/packages
> > >
> > >   $ECOS_REPOSITORY shows
> > bash:/ecoscvs/ecos/packages
> > >
> > >   Any suggestions on how to get past this?
> > >
> > >   Thanks,
> > >   spreet
> > 
> > You should be able to go to "Build->Repository"
> and
> > select where your
> > ecos.db file is stored.
> > 
> > -- 
> > Before posting, please read the FAQ:
> > http://ecos.sourceware.org/fom/ecos
> > and search the list archive:
> > http://ecos.sourceware.org/ml/ecos-discuss
> > 
> > 
> 
> 
> 
>        
>
____________________________________________________________________________________
> Choose the right car based on your needs.  Check out
> Yahoo! Autos new Car Finder tool.
> http://autos.yahoo.com/carfinder/
> 



       
____________________________________________________________________________________
Sick sense of humor? Visit Yahoo! TV's 
Comedy with an Edge to see what's on, when. 
http://tv.yahoo.com/collections/222

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2007-06-15 18:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16  0:19 spreet singh [this message]
2007-06-18 13:20 ` Paul D. DeRocco

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=264695.7453.qm@web62203.mail.re1.yahoo.com \
    --to=spreetsingh@yahoo.com \
    --cc=ecos-discuss@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).