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=WW/HvQ
	B1yKSJkqJMurmH93GezZVfunEolwiHz0cYNg8FEBl6Cu93F68oTgXLdzVFBvUqGT
	RHoXN/6UYV4+omeOWp4Nqr+PC6wfPAl5Nd/PkgkCd08coCjEymhp3R08Whx2GsUh
	cOBsQ3etCwTbWEisusHHJdRLK9+jI26oW+GfI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <545C919D.4070706@gmail.com>
Date: Fri, 07 Nov 2014 17:32:13 +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: Fwd: gcc-4.9.2-1 (x86_64) generates segfault during linking
References: <545BE242 DOT 7020507 AT free DOT fr> <545BE2E3 DOT 8030109 AT free DOT fr> <545BF836 DOT 8020204 AT gmail DOT com> <545BFD6B DOT 8060000 AT free DOT fr>
In-Reply-To: <545BFD6B.8060000@free.fr>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CxbeHc75LPdl2XeWGfSfURrH7KO7eafE7"

--CxbeHc75LPdl2XeWGfSfURrH7KO7eafE7
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 11/7/2014 06:59, Falk Tannh=E4user wrote:
> Am 06.11.2014 um 23:37 schrieb JonY:
>> On 11/7/2014 05:06, Falk Tannh=E4user wrote:
>>> Since I updated gcc from version 4.9.0-1 to 4.9.2-1, I obtain the error
>>>        collect2: Fehler: ld mit Signal 11 [Segmentation fault] beendet
>>> when compiling and linking a C or C++ program. However, an executable is
>>> generated and appears to work as expected.
>>> I installed the latest test release of cygwin so far (1.7.33-0.7).
>>
>> Does it somehow work if you link with gcc -fno-lto?
>=20
> Yes, this fixes the problem.
>=20

There seems to be some confusion in the __cxa_atexit in Cygwin 1.7.32,
basically 4.9.1 will only work with .32.

1.7.33 fixed the incorrect behavior that unfortunately broke gcc
__cxa_atexit usage. The next 1.7.33-0.8 should be more tolerant of the
old .32 behavior.

After 1.7.33 is officially released, gcc-4.8.3-4 and 4.9 will switch to
the standard conformant behavior.


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

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

iQIcBAEBAgAGBQJUXJGvAAoJEHE7X+KcFF1F1wYP/3+xRZpcfo6JCYwi37NBKRi/
SQJgkuEC4FB/vGE6iI9YgbvnqevqDseqBlFBrNmJMZe+Ltw5LzCP4S2ytYxn+etu
tsud7bJU8kpIebNOII0l4KTovrQg2Hp/+ohXcuNTCbrrvO1U///Ia55CffwCGFBZ
5cKOA7UHP6KTeSXAt16b2COH4N+0VtjTxQzKavxToIrwXIllh1Ng3+6oO1GENaxK
RqVXwA5cJHVnNg+GqxUYjSaBDDLK7U1W0Pd/9KSbWlswOddFQBLVSTegRDsJtOmF
mx/1KkpEkFWlrGOSMCgSR+WVSn094fy17ZXwAfUXxfNj+lRBGc9kT5Ylc1Uw22m6
V3OhMC54OiB7LnI90ybpRmXa+bF6IKlqpPsI1RcE+LHxVkXy0xxTjBeq8xfkNnnL
GkBsx7nvAWvBiDL+E5Hkvp71t5Lc71rytlAntrtNIkpBva3NDY7MZ5TeYV7cwpEG
ciVq4797qtSJhXZq3gKE77exxd3FsMkaEAX9+9Kk1SjW8YH/DqodY3C1pzo4lPxn
9i8FPf54xH5cbA+Kg0EeH2wFZ5SArCFV+V2FQVCGT4q1o1mEyhtj0jNWLi52DIDj
Um+cRDjNuUuBL+2e6xRuwsJl+38qrMZG/FgGZDoem3EyQO8bnB20cH7wwgvUCku0
pr7LHVqUXTPbwxYcv8JI
=YX+k
-----END PGP SIGNATURE-----

--CxbeHc75LPdl2XeWGfSfURrH7KO7eafE7--