X-Recipient: archive-cygwin@delorie.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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=n9M6IP
	a5NUO3d3plQPXSeYrBlLbAyEymamfW6QCgp5L0fZFue1vkEDw9fdMCmROT/Qooxs
	N977sG6oqdP0PdOxY+N4Xy1b6H8O61KbCAu8ukyrgDlxS4xqYhcAlBX1ITFAelC9
	bxtlsJQfzKXyDp3b7+iEfcXRz6YonZcCloyY0=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; s=default; bh=sNq3VHQaixX1
	oLgqo27VTT7mWeE=; b=QQ+RGctGKPZXDgBVXe+XzSoarX912EmFmuSw+uIFo4NK
	QOoqix+6W1qqWeyIltVzMEabGwX1tlwpKJWriZF0tXI0BA13IbDW7wJjBRyvIgeI
	JOyE/zFFRrPPiHd0Xuw2+28Kx9gClOJQ8+QHqqsttb2vcbZ7ZQH0xs1WWpKeT/w=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-pd0-f172.google.com
X-Received: by 10.67.15.40 with SMTP id fl8mr25248490pad.69.1404683968396;        Sun, 06 Jul 2014 14:59:28 -0700 (PDT)
Message-ID: <53B9C6B5.7080401@gmail.com>
Date: Mon, 07 Jul 2014 05:59:17 +0800
From: JonY <10walls@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:24.0) Gecko/20140503 FossaMail/24.5.0
MIME-Version: 1.0
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: cygwin64 problems after update: gcc 4.8.3-2, cygcheck -p
References: <53B85CC7.50500@posteo.net> <53B92D46.1070404@posteo.net>
In-Reply-To: <53B92D46.1070404@posteo.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="908lXFisUeBDxXeKAssWlpVt5cnRUM6pv"
X-IsSubscribed: yes

--908lXFisUeBDxXeKAssWlpVt5cnRUM6pv
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 7/6/2014 19:04, Lakhsa wrote:
> After some extended research and trials with a fresh OpenSSL master
> clone openssl32_trial this seems to be a problem of the cygwin ports of G=
CC.
> I've added some information about this - maybe one of the developers
> listening in on the OpenSSL project could have a closer look.
>=20

cygwin gcc has never been built with multilib support, I don't
know how it is possible that "it used to work".



--908lXFisUeBDxXeKAssWlpVt5cnRUM6pv
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBAgAGBQJTuca7AAoJEHE7X+KcFF1FQTMP/2vaaDhBmXX36CLBbjP3oRjp
uJwxVXF9fyqvQU8I5XwMrvOOK9dEVANLxNztEbHDkuVzQsSRBlqxG355gPLxYBi3
tdtSxwJdaqnt+wH44CTZzhvIs+X+/UtM6BwgdMc+ljEXMX6iGHE4TwavZpiNU+PH
q/O3MQI8i2PUwBxJfHBDQ8c8H8S1WvL0Jkmb9iLePil6iAfzCirf7y5YYTTd7Hh4
u91ySJbLAYt+rLDR2aHPHM5r2ZS1IOnckZgApKs/UuXlO6xwziJyGl26/JXbQ3zZ
Sa5rqFg7aMV/csgtXNTQ5/roH2wcJgtEJ7Uan3ZQDVd77NKJ4jxFcvJ+Wc1fORM6
SNrtH0HBNCXjR4W4ZrdX76TMVybvcRbzhZ/4oWmrXQshc2eb35dKSA6ycJNHpRtv
9/x0n6JwZpiLqCAV7tqjCzzGPho4QVMvuHM39MNN2qdKuD37rtK81NdILUz4jVD6
3bp7vfdeBQgRZTm6OIDjL42wPYpi9EpDNaMg08KH6KEdYKtyfp1dkVbmGtf/w7vo
v8sbjQEBOLRXRzO9RkuF/k83Br+Iuqim0koKgnHTY9h2bClcKF/k6tME3JZ7h0tI
+JZUttwKY1Hr7Pv64Ci+t/S5h1tPJOuwZun8R//aW/mfgkSagg9MrfsdE8mlexYf
fJ52VyzyCBfKRBpy8yG2
=SBTQ
-----END PGP SIGNATURE-----

--908lXFisUeBDxXeKAssWlpVt5cnRUM6pv--
