From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Problem with Cygwin 2.4.0-0.18 release
Date: Tue, 12 Jan 2016 12:34:00 -0000 [thread overview]
Message-ID: <20160112095023.GC15034@calimero.vinschen.de> (raw)
In-Reply-To: <CAFo71_78NFHNse7pDC0=kws4HbV+w_o9csHq0_-Hnk2=mxR3ZA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
On Jan 12 11:45, Ismail Donmez wrote:
> Hi,
>
> On Tue, Jan 12, 2016 at 11:28 AM, Corinna Vinschen
> <corinna-cygwin@cygwin.com> wrote:
> > Hi Ismail,
> >
> > On Jan 12 10:23, Ismail Donmez wrote:
> >> Hi,
> >>
> >> -0.17 was fine but this release breaks sshd, sshd.log says:
> >>
> >> 1 [main] sshd 2828 C:\cygwin64\usr\sbin\sshd.exe: *** fatal error - unable
> >> to load C:\Windows\system32\ws2_32.dll, Win32 error 1001
> >
> > What OS? 32 bit, 32 bit under WOW64 or 64 bit? How do you start sshd?
>
> Sorry for the brevity of my bug report. This is on Windows 7 SP1
> 64-bit with cygwin 64bit.
>
> > I'm asking because
> >
> > a) What I did was to revert a piece of code to the same state as in 2.2.1.
> > Does the "prev" version 2.2.1 work for you?
>
> I am always running cygwin snapshots on this machine and yesterday
> -0.17 was working fine. Now I rolled backed to 2.2.1-1 and it works
> fine. Went a little bit further and cygwin1-20160109.dll works fine
> where-as cygwin1-20160111.dll shows the problem.
Still, does 2.2.1 work for you, too?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-12 9:50 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 [this message]
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
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=20160112095023.GC15034@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).