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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=Zo/Gep
	/oKhj+qtDjX6vrnzdPkwM8likBu2h5JF4GV3SnXz1xWjJf3bSG4JfWWiS0+dbB4Z
	0eebrI10DDwT+TNHSXE69PJxriLsosfEg87vGkvlVerEBfuJE+Uj8JWMZ66YSkVl
	r2McqwAJAylSkftj/Ju2ZZINQxN1hNqzYSfBQ=
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=Uv8Wb8ddyDuv
	HTbBoXkPHbkkVLc=; b=P6IL61Fl0RfvQesgVzbh2UIq7Kk+th5RTCqGFhEakaey
	PjyTOoa/iH6rhy7MWeTXkHTOiV+MkjVr6Wp0SJqeLLVbJvMf1puHRhofW6MJDUEo
	JLRSHMT10SIqh8pX+ek9n1KOE5p/6KlHto8dkDpysIiXtdWlzDv2NC2GosFZZGs=
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=-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-f170.google.com
X-Received:	by 10.66.154.164 with SMTP id vp4mr20295135pab.4.1404610332575; Sat, 05 Jul 2014 18:32:12 -0700 (PDT)
Message-ID:	<53B8A6FF.3010804@gmail.com>
Date:	Sun, 06 Jul 2014 09:31:43 +0800
From:	JonY <10walls AT gmail DOT 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:	cygwin AT cygwin DOT com
Subject:	Re: cygwin64 problems after update: gcc 4.8.3-2, cygcheck -p
References:	<53B85CC7 DOT 50500 AT posteo DOT net>
In-Reply-To:	<53B85CC7.50500@posteo.net>
X-IsSubscribed:	yes

--gGNWPJThcSjQg9uXf9LcWLfBAwTWlgUHJ
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

On 7/6/2014 04:15, Lakhsa wrote:
> G'Day,
>=20
> after having updated my cygwin64 installation (Win7-64) for OpenSSL
> development I have encountered 2 problems:
>=20
>   * compiling for 32-bit with '-m32 -i686' now fails with internal
>     compiler error: in extract_insn, at recog.c:2154
>   * cygcheck -p [any_binary] produces a seg fault
>=20
> Both used to work until last update of the cygwin64-only setup end of
> June 2014 from FTP server at Uni Erlangen.

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




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

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

iQIcBAEBAgAGBQJTuKcTAAoJEHE7X+KcFF1F6XgP/2SxN01QVm7I8gPX6u3o+UVb
3F22/PJbCZTrcf5QzSOq4Ultk2YhUmq6UbJXrTbyjT7Tqu0ajVRj8iFUEUzrnRON
Bpf2W0RuagjuAU79pva+549mjeTeltjubJoRlArT79V3q1vA4TvC9k2F02AavR7p
MFDva/bhoMxfTSFlcimT/V/Fw2Pm1W8Sf4KV6ZGEq7oCv3lDPb8/qiVGeWMDfwsk
hZO9fTNYuicG5OovooXE2FMcQHIDgnIYJ2+DvywZEXBe/W4IOXvIzkMspn+QW2av
SbNFjfG6tJQaMtZnOBUAER+Drxef76AruZiNKO4oGGmgQqZJcNaeRMmij4fnPHBx
Nl/yKxHRUHBSgyEtwllJXiZMQBoqozsg2TRi97Aguz9H8RiJNWhAqdirNLNvjnJj
qUSKZGaXoypF3iYReroABm9W9DUBaepdRtuXaQegvXB+U3sr8YhXMVcQxpCOKocX
PuQxr6Uezt7T1bJsEaDWpfNq3U4qx7JwAQS8uZ9RmdfRu4xy/IlkukhdSP7fvY6W
6JwNsSUdbN4Iu3QychBHv9iaQFH/CdenVb0oRnfcLhNj6jq5iRqWpWQDC3CvsHIo
0sL8Hgq4fRX3i2UR+cj+3jGFI6EICRxvSczwKupg9PUzhNCkSFjBilz5h5J0VzzA
4g+pAkgP2+U8RUbyabkR
=3b+N
-----END PGP SIGNATURE-----

--gGNWPJThcSjQg9uXf9LcWLfBAwTWlgUHJ--

- Raw text -