public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: Updated: gcc-5.2.0-1 (Test x86/x86_64)
Date: Wed, 30 Sep 2015 23:36:00 -0000	[thread overview]
Message-ID: <560C71FB.4030005@tiscali.co.uk> (raw)
In-Reply-To: <560C6369.7060602@gmail.com>

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.

Dave.


--
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

  reply	other threads:[~2015-09-30 23:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <560BC46D.3060500@gmail.com>
2015-09-30 16:06 ` David Stacey
2015-09-30 22:34   ` JonY
2015-09-30 23:36     ` David Stacey [this message]
2015-10-01 13:04       ` cyg Simple
2015-10-06 16:26         ` Christian Franke
2015-10-06 17:51           ` Ken Brown
2015-10-06 22:12             ` David Stacey
2015-10-07  7:45               ` Csaba Raduly
2015-10-06 22:20           ` David Stacey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=560C71FB.4030005@tiscali.co.uk \
    --to=drstacey@tiscali.co.uk \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).