From: John Dallaway <jld@ecoscentric.com>
To: Tom Smithkowski <tom.smithkowski@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: Problem with Config Tool on Cygwin
Date: Thu, 15 Jun 2006 15:16:00 -0000 [thread overview]
Message-ID: <449179C5.2070503@ecoscentric.com> (raw)
In-Reply-To: <cba67f760606150806x5b1f504bkaf5fabe83b8e5867@mail.gmail.com>
Tom Smithkowski wrote:
>> This looks similar to the issue discussed at:
>>
>> http://www.cygwin.com/ml/cygwin-patches/2006-q2/msg00065.html
>>
>> As a workaround, it is currently possible to revert to version 1.5.18-1
>> of the "cygwin" package using the Cygwin Net Release Setup Program.
>>
>> Since the probable cause of this issue has been identified and patched,
>> I will wait for a new release of the Cygwin DLL before investigating any
>> further.
>
> Thank you for investigating this issue. Just to make sure I am
> understanding correctly, your conclusion is that this is due to a
> cygwin bug, and that you would expect that to be fixed in a future
> release. Therefore, no changes to configtool are required at this
> time.
That is my hypothesis, yes.
John Dallaway
eCosCentric Limited
--
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:[~2006-06-15 15:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 16:55 [ECOS] " Tom Smithkowski
2006-06-15 8:34 ` [ECOS] " John Dallaway
2006-06-15 12:25 ` John Dallaway
2006-06-15 15:06 ` Tom Smithkowski
2006-06-15 15:16 ` John Dallaway [this message]
2006-06-15 15:53 ` Andy Jackson
2006-06-15 17:22 ` [ECOS] eCos & RedBoot on AT91SAM7S Evgeny Belyanco
2006-06-15 17:32 ` Andrew Lunn
2006-06-15 17:47 ` Re[2]: " Evgeny Belyanco
2006-06-15 18:53 ` Andrew Lunn
2006-06-15 20:55 ` Re[2]: " Evgeny Belyanco
2006-06-15 22:59 ` Laurie Gellatly
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=449179C5.2070503@ecoscentric.com \
--to=jld@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=tom.smithkowski@gmail.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).