public inbox for
 help / color / mirror / Atom feed
From: "Michael W. Ellis" <>
To: <>
Subject: [ECOS] eCos installation instructions
Date: Mon, 05 Oct 2015 16:22:00 -0000	[thread overview]
Message-ID: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02AD60EB@exchange> (raw)

I am attempting to install the eCos development tools on a Win7 64-bit machine and have quickly encountered problems attempting to follow the installation instructions.  I come from a hardware background  but have written quite a bit of embedded software, but I'm not familiar with eCos, Cygwin, Eclipse and all the related tools, so consider me a total newbie with regards to eCos.

I am attempting to follow the instructions at and the first step is to install Cygwin.  Following the instructions on I have downloaded and launched the 32-bit version of the Cygwin installer.  The instructions then say to install the following packages:

gcc4 - see below
libexpat1 - found under Libs
libmpc1 - see below
make - found under Devel
patch - found under Devel
sharutils - found in Archive
tcl - found under Interpreters
wget - found under Web

Searching for gcc4 yields no results.  Searching for gcc vields many results (cygwin64-gcc-*, gcc-*, mingw64-i686-gcc*, mingw64-x86_64-gcc-*) under the Devel category, and libgcc1 under the Libs category.  What is the appropriate choice for gcc4?  I assume that these are different toolchain options but I have no idea whether eCos requires a particular choice.

The library libmcp1 was not found.  Searching for libmpc yielded libmpc3 - am I to assume that this is an appropriate substitution?



Before posting, please read the FAQ:
and search the list archive:

             reply	other threads:[~2015-10-05 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 16:22 Michael W. Ellis [this message]
2015-10-09  7:22 ` [ECOS] " John Dallaway

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02AD60EB@exchange \ \ \

* 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).