From: Ismail Donmez <ismail@i10z.com>
To: cygwin@cygwin.com
Subject: Re: Problem with Cygwin 2.4.0-0.18 release
Date: Wed, 13 Jan 2016 15:01:00 -0000 [thread overview]
Message-ID: <CAFo71_6mAk9YFL-3SrvqR0eZy807OEWzmrdpMkRepepqwrnprQ@mail.gmail.com> (raw)
In-Reply-To: <20160113104518.GA16198@calimero.vinschen.de>
On Wed, Jan 13, 2016 at 12:45 PM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> On Jan 13 09:59, Ismail Donmez wrote:
>> Hi,
>>
>> On Tue, Jan 12, 2016 at 5:05 PM, Corinna Vinschen
>> <corinna-cygwin@cygwin.com> wrote:
>> > I tried to workaround this problem by "upgrading" the DLL load
>> > mechanism to use the facilities available since Vista. In theory
>> > this should work fine for you. I uploaded a new developer snapshot
>> > to https://cygwin.com/snapshots/ Please give it a try.
>>
>> Sadly still getting the same error.
>
> That doesn't make sense. The new code has a fallback which is identical
> to the code in -0.17. No offence, but are you *sure* you're using the
> snapshot DLL? Uname on 64 bit should print:
>
> $ uname -srvm
> $ CYGWIN_NT-6.1 2.4.0(0.293/5/3) 2016-01-12 14:54 x86_64
Sorry for that, indeed somehow it overwrite the cygwin1.dll I guess
because I ran setup.exe first and it re-installed -0.18 and then I
manually overwrited cygwin1.dll but somehow failed.
Anyhow it works now, thanks!
Regards,
ismail
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-01-13 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 9:34 Ismail Donmez
2016-01-12 9:45 ` Corinna Vinschen
2016-01-12 9:50 ` Ismail Donmez
2016-01-12 12:34 ` Corinna Vinschen
2016-01-12 12:35 ` Ismail Donmez
2016-01-12 15:39 ` Corinna Vinschen
2016-01-13 9:58 ` Ismail Donmez
2016-01-13 11:01 ` Achim Gratz
2016-01-13 11:02 ` Corinna Vinschen
2016-01-13 15:01 ` Ismail Donmez [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=CAFo71_6mAk9YFL-3SrvqR0eZy807OEWzmrdpMkRepepqwrnprQ@mail.gmail.com \
--to=ismail@i10z.com \
--cc=cygwin@cygwin.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).