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=ZbkNv7
	OVZ4P2/t400fsB28mWAUg21GXF3RT0xHc7nK7MbBbA2ZZ7dO0G/2a18J273Qx7qj
	vqQVR+Qng9T7fHs5UPmx27ApcVBeLOs+Xq3x1rZG62tzXfv03t19uzri2ZWqGXlN
	4u32EEmLOpq0nopyI8Db9HuFCNSchJ6zVVQk8=
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: <5458009E.6030007@gmail.com>
Date: Tue, 04 Nov 2014 06:24:30 +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: gcc packaging bug?
References: <5457F7C2 DOT 9090204 AT cornell DOT edu> <5457FC00 DOT 5080907 AT gmail DOT com> <5457FDAF DOT 9050408 AT cygwin DOT com>
In-Reply-To: <5457FDAF.9050408@cygwin.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="64kERupPVCRdVIxLJ2NW72JipQKRTutTS"

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

On 11/4/2014 06:11, Yaakov Selkowitz wrote:
> On 2014-11-03 16:04, JonY wrote:
>> On 11/4/2014 05:46, Ken Brown wrote:
>>> The setup.hint files for gcc and its subpackages now say
>>>
>>> curr: 4.8.3-2
>>> prev: 4.8.3-3
>>> test: 4.9.2-1
>>>
>>> I assume this is a typo; it causes everyone who is not installing the
>>> test release to get downgraded from 4.8.3-3 to 4.8.3-2.
>>
>> No, this is deliberate, 4.8.3-3 is bugged, it could not build later
>> versions of gcc.
>=20
> How so?

As explained in the other email, it made failed link test return $? 0
anyway. This broke the stage 1 libgcc configure tests.

Reverting to an older version of gcc and then using it to build 4.9.2-1
succeeded. I also used 4.9.2-1 to build a copy of itself as test, seems
like it works. The only real change was changing atexit use to
__cxa_atexit in libgcc.

Corinna mentioned some problems with gcc misoptimizing atexit over IRC.


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

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

iQIcBAEBAgAGBQJUWACvAAoJEHE7X+KcFF1FpIgP/0SB1kzFy3XZt6gNS+m4NL5P
MkwuJ66zCBykxFW5Lc5d73bgSODpQjTr571RgSpaLJIOPSwGpFVj8QDaA5zsHVaj
JeWaoa70H40YuqcwXrcnE6LSoKCGjqqmUAAB3gMjkbHnEgHiCwrAde1RtQY15GKn
WQ7gqt5heHnGBMbDkPWqIPQZZMCb3FzvTTfpKeaGTC/LDwLUWgZqYXTT2N9lzvFK
FebNO6CRwWAbd6/l+RgHwhKNdO+qaxq+Y4IT7LpMk6ldxHDXNrAgVUcnZKckE09l
I6AXQepJtx1mIuw+5QB8sY67G2bfJSfeLRNhQ4F27GfMdRcJ5FnhC2g7nYnIchiM
BWS6CIfViOjWZZt+zGZGk6UFLULz6cvR5G8RYv8JbZJBKFkhOVEEIFdTRsp/p0B5
m7N2IsTlMAYhvlWXDAOrd3bFEmJVRSLDAC6zsrR7XE30jqeUcf864pjGEW1ofjSC
uvLySFfaT2iNskSfCUlO0BxwRiAb9xPGfdIQpdjpdn8sqTenAalh7tg9/zpH+qqq
kXk4dR4aVeD2eKNxytfGS9U8erLSe7f736ZH9ryrMmFKNVILO7/tv8T6phEuPoxa
remdH8pZRiVMg+hjx/KyBAlxQWwtn4SIIL986rVjt/a2cCTJywZx7JalsXW0DByK
aW2/zOtt7dsAiICJWzR/
=f+wz
-----END PGP SIGNATURE-----

--64kERupPVCRdVIxLJ2NW72JipQKRTutTS--