public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Jérémy Alles" <jeremy.alles@orange-ftgroup.com>
Cc: Gentleman.nbg@gmx.de, ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] RE: eCos configtool doesn't work on cygwin
Date: Wed, 06 Feb 2008 14:36:00 -0000	[thread overview]
Message-ID: <47A9C5E7.500@mlbassoc.com> (raw)
In-Reply-To: <200802061407.m16E7LtV022886@smtp.silicomp.fr>

Jérémy Alles wrote:
> Hi there,
> 
> I'm a new user to eCos (I started to work with it yesterday !) and I had the
> same problem (configtool under Cygwin not working). I solved this problem by
> using an up-to-date version of configtool that I downloaded from this page:
> http://www.ecoscentric.com/devzone/configtool.shtml

I'd also *strongly* suggest using the anonymous CVS - eCos 2.0 is approaching
6 years old.

Also, Mr "Gentleman.nbg" (real names are preferred here!), you'll need to
port eCos to your platform.  Starting from the most up to date sources
would be a wise move.

> -----Message d'origine-----
> De : ecos-discuss-owner@ecos.sourceware.org
> [mailto:ecos-discuss-owner@ecos.sourceware.org] De la part de
> Gentleman.nbg@gmx.de
> Envoyé : mercredi 6 février 2008 14:56
> À : ecos-discuss@ecos.sourceware.org
> Objet : [ECOS] eCos configtool doesn't work on cygwin
> 
> Hello eCos-Team,
> 
> I am currenty trying to build a eCos System with an application that I wrote
> for my studies.
> Now I have a problem with the configtool under Cygwin.
> 
> I downloaded a eCos 2.0 source, where there is a configtool.exe in
> ecos-2.0/tools/bin when executing it under cygin nothing happens. not even a
> message from shell.
> 
> Then I read that there are some problems with recent cygwin versions, so I
> tryied to execute the unsupported snapshot of the configtool that should
> work with the recent cygwin version. This configtool doesnt execute eather.
> 
> I found an Windows version of configtool that I could install and even run
> under Windows, but I don't know if I should use it.
> My target is a Freescale MPC5516 microcontroller, that should be able to run
> eCos 2.0. In the templates I don't know what to choose.
> 
> What do u suggest? How can I make a build of eCos now?
> 
> Thank you very much
> 


-- 
------------------------------------------------------------
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

  reply	other threads:[~2008-02-06 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 13:56 [ECOS] " Gentleman.nbg
2008-02-06 14:07 ` [ECOS] " Jérémy Alles
2008-02-06 14:36   ` Gary Thomas [this message]
     [not found]     ` <20080207161256.176260@gmx.net>
2008-02-07 16:23       ` Gary Thomas
2008-02-08  8:50 [ECOS] Fwd: " Gentleman.nbg
2008-02-08  9:22 ` [ECOS] " John Dallaway
2008-02-08 18:08   ` Paul D. DeRocco
2008-02-14 17:11   ` Gentleman.nbg

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=47A9C5E7.500@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=Gentleman.nbg@gmx.de \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=jeremy.alles@orange-ftgroup.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).