DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=A6y6fXbPecwW8jNx
	wR926AGDhS+Li+gnINXfSlqdElHxiE0nxI7PutS8mR9enTace4OJgSKf+hFjSeXT
	IVSAt/amkRoHzDhLVfhndnZ6fg6KfnLODgsm8Tn5NtTj/+zzCxGsDAfr7DDbcgWg
	gPJcHQ+w/RjC7uCO4/J7ucU8v40=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Updated: gcc-5.2.0-1 (Test x86/x86_64)
To: cygwin@cygwin.com
References: <560BC46D.3060500@gmail.com> <560C0863.70505@tiscali.co.uk> <560C6369.7060602@gmail.com> <560C71FB.4030005@tiscali.co.uk>
From: cyg Simple <cygsimple@gmail.com>
Message-ID: <560D2F6D.90608@gmail.com>
Date: Thu, 1 Oct 2015 09:04:45 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <560C71FB.4030005@tiscali.co.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

On 9/30/2015 7:36 PM, David Stacey wrote:
> On 30/09/15 23:34, JonY wrote:
>> On 10/1/2015 00:05, David Stacey wrote:
>>> On 30/09/15 12:15, JonY wrote:
>>>> gcc-5.2.0-1 has been uploaded for 32bit and 64bit Cygwin.
>>>>
>>>> This is the first series of the 5.x releases, and should be considered
>>>> as experimental as such.
>>>
>>> Have you managed to work around the ABI change in gcc-5 [1], or will
>>> this require a mass rebuild at the point gcc-5 becomes 'current'?
>>>
>>> [1] -http://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/
>> As far as I know, every gcc release will break C++ ABI, so it would mean
>> rebuilding everything C++.
> 
> According to the Red Hat blog above, the last time g++ caused an ABI
> change was back in the 3.x days, so it hasn't happened for a while. Ah
> well, we have maintainers for most packages in Cygwin, so we'll have to
> co-ordinate a rebuild.

Regardless, JonY is correct.  Every C++ release, regardless of the
vendor, causes an ABI break with shared libraries and the naming of the
object elements (mangled names).  It is the nature created by technical
reason.  Not to mention that the first paragraph of the release states
that there is an ABI break.  And then there is this paragraph: "So the
plan for this ABI change has been to leave the soname (and the existing
binary interface) alone, and express the new ABI using different mangled
names."

-- 
cyg Simple

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple