From: "Andrew Hannam" <andrewh@inmarket.com.au>
To: "'eCos Discussion'" <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Problems installing on Windows 7 x64
Date: Mon, 16 Apr 2012 02:38:00 -0000 [thread overview]
Message-ID: <006901cd1b79$f9748c10$ec5da430$@com.au> (raw)
In-Reply-To: <CAJXPg6+JBkTkU-Py1fZsYxGw5L0BTFKi7duvsQ-JpQs28ELLKw@mail.gmail.com>
In c:\cygwin\bin
Copy libtcl8.5.dll to tcl84.dll
This fixed it for me.
-----Original Message-----
From: Fabrizio Carrai [mailto:f.carrai@libero.it]
Sent: Saturday, 14 April 2012 11:56 PM
To: eCos Discussion
Subject: Re: [ECOS] Problems installing on Windows 7 x64
Solved with the latest CYGWIN update.
Now another problem show up:
$ configtool.exe
-bash: /opt/ecos/ecos-3.0/tools/bin/configtool.exe: Bad address
I also installed the latest cygwin snapshot but with no joy. Any suggestions
?
F.
Il 14 aprile 2012 12:06, Fabrizio Carrai <f.carrai@libero.it> ha scritto:
> Same problem to me, with the same Windows configuration. Moreover at
> the start, sometimes I got the error
>
> $ sh ecos-install.tcl
> eCos installer v2.0.1 starting...
> Written and maintained by Jonathan Larmour <jifl@eCosCentric.com>
>
> Retrieving installer metadata information...
> 0 [main] tclsh8.5 1316 child_info_fork::abort: libtcl8.5.dll:
> Loaded to different address: parent(0x5E0000) != child(0x590000)
> 0 [main] tclsh8.5 3240 child_info_fork::abort: libtcl8.5.dll:
> Loaded to different address: parent(0x5E0000) != child(0x410000)
> 0 [main] tclsh8.5 3836 child_info_fork::abort: libtcl8.5.dll:
> Loaded to different address: parent(0x5E0000) != child(0x410000)
>
> *** ecos-install.tcl error: Failed to retrieve metadata:
> couldn't fork child process: resource temporarily unavailable
>
> This message is in copy to the author: available for any further test.
> Thanks in advance.
>
> F.
>
> Il 14 aprile 2012 01:32, Andrew Hannam <andrewh@inmarket.com.au> ha
scritto:
>> When trying to install on Windows 7 x64 I got the following message
>> after picking the distribution site and the install directory...
>>
>> Available prebuilt GNU tools:
>>
>> *** ecos-install.tcl error: *** ecos-install.tcl error: can't read
>> "ecos_install::toolchains(CYGWIN_NT-6.1-WOW64)": no such element in
>> array
>>
>> What do I need to do to resolve this?
>> PS. Searched Archives but couldn't find anything similar.
>>
>>
>> --
>> Before posting, please read the FAQ:
>> http://ecos.sourceware.org/fom/ecos
>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>>
--
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:[~2012-04-16 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 23:33 Andrew Hannam
2012-04-14 10:06 ` Fabrizio Carrai
2012-04-14 12:37 ` Fabrizio Carrai
2012-04-16 15:37 ` Jonathan Larmour
2012-04-16 17:19 ` Fabrizio Carrai
2012-04-14 13:56 ` Fabrizio Carrai
2012-04-16 2:38 ` Andrew Hannam [this message]
2012-04-16 14:18 ` [ECOS] " John Dallaway
2012-04-16 17:32 ` [ECOS] " Fabrizio Carrai
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='006901cd1b79$f9748c10$ec5da430$@com.au' \
--to=andrewh@inmarket.com.au \
--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).