From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 65977 invoked by alias); 1 Oct 2015 13:04:37 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 65965 invoked by uid 89); 1 Oct 2015 13:04:36 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_20,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-qg0-f48.google.com Received: from mail-qg0-f48.google.com (HELO mail-qg0-f48.google.com) (209.85.192.48) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 01 Oct 2015 13:04:31 +0000 Received: by qgt47 with SMTP id 47so64081994qgt.2 for ; Thu, 01 Oct 2015 06:04:29 -0700 (PDT) X-Received: by 10.55.26.14 with SMTP id a14mr3596243qka.99.1443704669038; Thu, 01 Oct 2015 06:04:29 -0700 (PDT) Received: from [192.168.0.7] (d27-96-48-76.nap.wideopenwest.com. [96.27.76.48]) by smtp.gmail.com with ESMTPSA id 18sm2358445qgg.39.2015.10.01.06.04.28 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Oct 2015 06:04:28 -0700 (PDT) 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 X-Enigmail-Draft-Status: N1110 Message-ID: <560D2F6D.90608@gmail.com> Date: Thu, 01 Oct 2015 13:04:00 -0000 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 X-IsSubscribed: yes X-SW-Source: 2015-10/txt/msg00002.txt.bz2 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