X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=pkKmexh/eU+Oi6Arh+5qRyJsoZl1dm5ez/umKVw4xPWDFJyFowdpp
	BdfBc6noBAgYzq9OdjLdzsHyZTnhGFzIG6ppJct1NXjXYiTZ8hrPYI5QohVeYpM9
	sNWKDxHDNbEcvuYEoyvGw4iatxKr8SjCa/O/9fM6LkUbSg7agm5qR8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=zCyhNcCHXurbH5/L5JNaVeFLF1w=; b=CyufEJH9DHMQRx1OM4q65eVJYS0x
	3ka0+k+6o9e838bhTlYthXbAYF/m9/TtWTqob+XW4dPJqUGazRUuKZHqlxrVIQh9
	6WAUDx+uzAqFmZQtk+WjMjjGb3AGL6S/dH/H4jHu2gShSVswhG5BEu/MXCr8KHti
	DcPnYS2KHHHygao=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-93.0 required=5.0 tests=AWL,BAYES_20,KAM_LAZY_DOMAIN_SECURITY,KHOP_DYNAMIC,RCVD_IN_BRBL_LASTEXT,RCVD_IN_PBL,RDNS_DYNAMIC,USER_IN_WHITELIST autolearn=no version=3.3.2 spammy=H*i:sk:7i_EJws, H*f:sk:7i_EJws, H*MI:sk:7i_EJws, Hx-languages-length:1920
X-HELO: calimero.vinschen.de
Date: Tue, 12 Jan 2016 16:05:38 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problem with Cygwin 2.4.0-0.18 release
Message-ID: <20160112150538.GE15034@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAFo71_69T7m0_SK2DmFpuJxyhCYdOTLeeGYRcpo8rY2uk+Q=8Q AT mail DOT gmail DOT com> <20160112092831 DOT GA15034 AT calimero DOT vinschen DOT de> <CAFo71_78NFHNse7pDC0=kws4HbV+w_o9csHq0_-Hnk2=mxR3ZA AT mail DOT gmail DOT com> <20160112095023 DOT GC15034 AT calimero DOT vinschen DOT de> <CAFo71_4dTguerd5Sh3NX8OrHFgo9zpYcqw6R5PCE=7i_EJwsUw AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="9UV9rz0O2dU/yYYn"
Content-Disposition: inline
In-Reply-To: <CAFo71_4dTguerd5Sh3NX8OrHFgo9zpYcqw6R5PCE=7i_EJwsUw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)

--9UV9rz0O2dU/yYYn
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jan 12 11:54, Ismail Donmez wrote:
> On Tue, Jan 12, 2016 at 11:50 AM, Corinna Vinschen
> <corinna-cygwin AT cygwin DOT com> wrote:
> > On Jan 12 11:45, Ismail Donmez wrote:
> >> Hi,
> >>
> >> On Tue, Jan 12, 2016 at 11:28 AM, Corinna Vinschen
> >> <corinna-cygwin AT cygwin DOT 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 ss=
hd?
> >>
> >> 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?
>=20
> Quoting my email "Now I rolled backed to 2.2.1-1 and it works fine."

That's what time pressure does to my reading skills... sorry :}

This is a bit weird.  If 2.2.1 using the same method works, why not
2.4.0-0.18?!?

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.


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--9UV9rz0O2dU/yYYn
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWlRZCAAoJEPU2Bp2uRE+gzsIP/Rv9YbnkZMZEgWFzNTsVAEk2
ipUcrVottW3Txg+LdcwC6cOcwH9LjPXXa7cu0s0m46lNj4ifFMjfGae+SqmxQ6ZV
rWWZjcPiVlv4JQmL6pigchK4epSki6q9XKS71pimyhweRc0eP9udTHL7lIX5DsAU
pbCFAlbWef7PRg3/a3XotpJJ13wlYgctEsnerMsXqsd3YtkCCQ6rh/RIhY0SUa1X
qeUhX4qaRV7c0HmZdAzmRV0jmThV4KN7wpwORIsw0QrifqANyxpPkc9e+Ww/cn0z
jvD/A+dAJrWyjn4fL6qIp554y7cjz0zrNZJGwKKckU7HLn5m34yaZKAW/cXshthO
pv36bMqzRzpHbtUv++vRiMbELVMdQKcv1qWk9O49XNgbsEcNhtdUt8wRa2PDx4Cn
X5UPhV29vvSyBhfzDMHAStTtwEyB1SDn5roawA1I41XpuNAqU+O6/k2Ju0sI1shm
Bp96jKa5LnD/wU4VqcLCzKEZc1YtaHAH5A5ppGbNP1ywGVc0KUd31lg4sjK1GkKU
7JY0dmjpQpln7tFaEhe08rShIH6g6ueV86RdGhm9n9ajXsCxkUhyIHC7I/9HeQUa
7WvNoJQt3zEqnQwq943sTelTwRpGNRQ5+XC01rczLNtfqFucpOxgTXVAUaZ7gogV
2FcHCTS81FzS9kVIitHN
=BO+W
-----END PGP SIGNATURE-----

--9UV9rz0O2dU/yYYn--