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=S0XBm6
	gEHVcmrXIPxzJZVQBIhvw0IG5r/n0MproEbw3zL7DxAGnr+7eDBvPywt2LQd27c/
	Ste8JrD4rhE+F4c4yGEMuXNUFwbhNLYupnB6flZ3cYwELBA6H41CyhYj+9UTbZ6k
	bnLom0EsCSSy4LT3FMyvBHJu4pIb+CS/MIoyw=
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=bU6TuUi4RZBs
	6FyA1s98Rx1m4jo=; b=un6qLIypKvhvQNqeg1fQNoMmBVqlEoG7PIk1CWp1PKMF
	5wgcAPJoZFOrH/Q0RQjJyDLjeLDMAEjwNcxO/UMUKmBiHK2bgvV3Z2qhN2dQaUMl
	0rypAmFTtVAu14wMoJu+zAiyDu7kHZFyqWQgdYSGM4MMxO+ilVqfxELhP0gXTZc=
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=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-pa0-f41.google.com
X-Received:	by 10.66.160.193 with SMTP id xm1mr6092947pab.115.1415052683961; Mon, 03 Nov 2014 14:11:23 -0800 (PST)
Message-ID:	<5457FD85.3060406@gmail.com>
Date:	Tue, 04 Nov 2014 06:11:17 +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>
In-Reply-To:	<5457FC00.5080907@gmail.com>
X-IsSubscribed:	yes

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

On 11/4/2014 06: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.
>=20
> No, this is deliberate, 4.8.3-3 is bugged, it could not build later
> versions of gcc.
>=20

I forgot to mention 4.8.3-4 will be uploaded soon to fix the problem
atexit use in libgcc. It was causing configure failures in stage1 libgcc
by causing link test to return $? 0 even if it failed.




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

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

iQIcBAEBAgAGBQJUV/2GAAoJEHE7X+KcFF1FNQIP/3lYwCR/lkeg57IVi6YjqQ/b
zuTU/hTrzFXoB+RbUoSqcAGi8XdzIW8wfHIwdZyfRjSKArjcrpCq07RbjuOlZfQR
sDmTBZF6UormkHDLXaE3Z8gqXbOCHGp4L3of/9uwYTuw6+8gdaPxDrZQCG9KkfXb
741pIXfk43t7aGNsuC8yIXuZoB/sYrG7wLP9g/dCw0eemaKYNQVJxsJ90QAv3E3v
EtxpVYMPojUKtS6kXkA4BP0Gk3wOoZvZwdHh+wbCL5EBrqN5xD/6AWp0v5kH3mT/
wLnoc966z0OiTCoj/2SsDbIbsQZQeILFCf0VLyTpLCGG+JvndNGA0a8K84MgL8S6
RzSGEWstaKHKZl8zfwhOvYIKC8+WEgJEYxRvTNVNl8bIbontsE41Ns44qHgF+hEA
4S0hcyY11LflGW2v0duFI2cfqCcZj6+1XAS+Md3lA/T2hIWMtXRWpt7DCWoqZwzA
E5oU358LtmOlQpjVqdDujd3V1jrJM7dWUC6ylnMLmp+PfxPaK1krU1tjUjx9PVN8
Goi6z3T9dkOiCr/kiIUZVwrW+X0eLi3xSFrdG2cmn4/qM1IYmNnoIsdJxC0esOdW
LPhulw+XWHVrBTDPGmQ/UWVrBNW5eFS/cZRyE0GQgLyqnczKISG37FsxrZRuBRLQ
MrFPKJYId7DXvKpraOo6
=aza+
-----END PGP SIGNATURE-----

--xfcAVn3dp2pecmnfmbXSjUMs7BauOutQA--

- Raw text -