From: "Max Seidenstücker" <max.seidenstuecker@googlemail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: Stephen Finney <shf@pfinc.com>,
eCos Discussion <ecos-discuss@sourceware.org>
Subject: Re: [ECOS] Re: missing libmpfr1 in cygwin 64 bit installation
Date: Thu, 22 Aug 2013 08:52:00 -0000 [thread overview]
Message-ID: <CAASVbFFLsr05CMFdwnX6JPakuRJukinHL1rKG1HD+ud9k+y8nQ@mail.gmail.com> (raw)
In-Reply-To: <5215CFA0.5000901@dallaway.org.uk>
John is right, just use Cygwin 32-bit isntead of 64-bit. There might
be an issue with building in Windows with the newest TCL8.5 libary and
cygwin1.dll that use the same namespace.
This helped the colleagues having this problem recently:
http://stackoverflow.com/questions/9300722/cygwin-error-bash-fork-retry-resource-temporarily-unavailable
2013/8/22 John Dallaway <john@dallaway.org.uk>:
> Hi Stephen
>
> On 21/08/13 19:35, Stephen Finney wrote:
>
>> My latest computer is Windows 7 64 bit. I installed 64 bit cygwin so that
>> I can continue developing my ecos project. The "Installing Cygwin for use
>> with eCos" page specifically says to select libmpfr1 (and others). But
>> the 64 bit cygwin installer only has libmpfr4. I selected that package
>> and continued with the installation.
>>
>> After installing the arm-eabi cross compiler, I find that it will not run.
>> At a cygwin prompt, I typed "/op/ecos/gnutools/arm-eabi/bin/arm-eabi-gcc
>> -version" and got nothing back before a new prompt. It seems that
>> libmpfr1 is required for the eCos toolchains to run.
>
> Yes, libmpfr1 is required.
>
>> Can anyone tell me how to fix this problem?
>
> The Cygwin-hosted eCos toolchains were built before 64-bit Cygwin was
> available. These toolchains run just fine with a 32-bit Cygwin
> installation on 64-bit Windows 7 so, as a workaround, you might attempt
> a parallel installation of 32-bit Cygwin (including libmpfr1) on your
> new PC. It would be helpful to report back to this list.
>
> In the longer term, we will need to re-build the toolchains against
> libraries provided by 64-bit Cygwin.
>
> I hope this helps...
>
> 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
>
--
Beste Grüße / best regards
Max Seidenstücker
Marienbader Straße 36
93057 Regensburg
Telefon.: +49 941 99227088
Mobil: +49 160 97646661
Mail: max.seidenstuecker@googlemail.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2013-08-22 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 18:35 [ECOS] " Stephen Finney
2013-08-22 8:45 ` [ECOS] " John Dallaway
2013-08-22 8:52 ` Max Seidenstücker [this message]
2013-08-23 14:44 ` [ECOS] " Stephen Finney
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=CAASVbFFLsr05CMFdwnX6JPakuRJukinHL1rKG1HD+ud9k+y8nQ@mail.gmail.com \
--to=max.seidenstuecker@googlemail.com \
--cc=ecos-discuss@sourceware.org \
--cc=john@dallaway.org.uk \
--cc=shf@pfinc.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).