From: John Dallaway <john@dallaway.org.uk>
To: "Michael W. Ellis" <mellis@pesa.com>
Cc: eCos Discussion <ecos-discuss@sourceware.org>
Subject: [ECOS] Re: eCos installation instructions
Date: Fri, 09 Oct 2015 07:22:00 -0000 [thread overview]
Message-ID: <56176B12.5000403@dallaway.org.uk> (raw)
In-Reply-To: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02AD60EB@exchange>
Michael
On 05/10/15 17:22, Michael W. Ellis wrote:
> Following the instructions on
> http://ecos.sourceware.org/cygwin.html 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?
It looks like the Cygwin gcc4 and libmpc1 packages have been withdrawn.
I suggest you try the gcc-core and libmpc3 packages instead. You may
need to create /bin/cygmpc-1.dll as a symbolic link to /bin/cygmpc-3.dll
in order to satisfy the dependencies of the eCos toolchains. Does this
work for you?
John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2015-10-09 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 16:22 [ECOS] " Michael W. Ellis
2015-10-09 7:22 ` John Dallaway [this message]
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=56176B12.5000403@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@sourceware.org \
--cc=mellis@pesa.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).