From: Ryan Hill <rhill@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: moving gcc-5.2 to unstable
Date: Fri, 2 Oct 2015 02:21:09 -0600 [thread overview]
Message-ID: <20151002022109.1f211ef9@caribou.gateway.pace.com> (raw)
In-Reply-To: 20151001134947.GM5374@vapier.lan
[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]
On Thu, 1 Oct 2015 09:49:47 -0400
Mike Frysinger <vapier@gentoo.org> wrote:
> what do people want to have in place before we move gcc-5.2 into ~arch ?
>
> the general list looks pretty good:
> https://bugs.gentoo.org/536984
IMO these should be fixed before we unmask:
546742: x11-apps/sessreg-1.1.0 fail to build with gcc5
547626: dev-lang/python-3.3 / 3.4 test_faulthandler hangs with GCC 5.1
547950: app-shells/zsh-5.0.7-r2 builds but has runtime errors with GCC 5
555866: media-libs/phonon-4.8.3-r1[qt5] fails to build with gcc-5
Just because they're common packages that lots of people will have installed.
Also they all have patches.
> the only glaring issue is the C++11 ABI breakage:
> https://bugs.gentoo.org/542482
>
> we already posted a news item when the breakage started in gcc-4.7:
> https://archives.gentoo.org/gentoo-dev/message/4fa0c84858b4df49668da20302fc5b6f
>
> but since gcc-5.x makes this the new default standard, more people are going
> to run into it, so we probably want a reminder. do we want any sort of
> automation otherwise here ?
I think we need a news item to remind people they really do have to emerge -e
@world after this one or they could have a bad time.
FWIW I updated one system from 4.9 to 5.2 by rebuilding ~700 packages in random
order just to see how bad the ABI breakage would be and only ran into it once.
I may have just gotten lucky though.
--
Ryan Hill psn: dirtyepic_sk
gcc-porting/toolchain/wxwidgets @ gentoo.org
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 475 bytes --]
next prev parent reply other threads:[~2015-10-02 8:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 13:49 [gentoo-dev] moving gcc-5.2 to unstable Mike Frysinger
2015-10-01 14:11 ` Alexandre Rostovtsev
2015-10-01 14:24 ` Mike Frysinger
2015-10-01 15:10 ` Alexandre Rostovtsev
2015-10-01 14:34 ` Georg Rudoy
2015-10-01 20:04 ` Anthony G. Basile
2015-10-02 8:21 ` Ryan Hill [this message]
2015-10-02 13:56 ` [gentoo-dev] " Mike Frysinger
2015-10-02 14:27 ` Mike Gilbert
2015-10-02 14:44 ` Brian Evans
2015-10-03 2:13 ` [gentoo-dev] gcc-5 news item wrt C++ ABI Mike Frysinger
2015-10-03 4:53 ` [gentoo-dev] " Ryan Hill
2015-10-03 5:04 ` [gentoo-dev] " Jason Zaman
2015-10-03 8:37 ` [gentoo-dev] " Ryan Hill
2015-10-03 12:38 ` [gentoo-dev] " Ciaran McCreesh
2015-10-03 17:24 ` Mike Frysinger
2015-10-03 17:30 ` Ciaran McCreesh
2015-10-05 18:43 ` Paweł Hajdan, Jr.
2015-10-06 4:43 ` Mike Frysinger
2015-10-03 23:16 ` hasufell
2015-10-03 23:53 ` Anthony G. Basile
2015-10-04 3:58 ` [gentoo-dev] " Duncan
2015-10-20 18:17 ` [gentoo-dev] " Mike Frysinger
2015-10-06 4:49 ` Mike Frysinger
2015-10-06 5:43 ` Michał Górny
2015-10-05 18:45 ` Paweł Hajdan, Jr.
2015-10-05 19:20 ` Jason A. Donenfeld
2015-10-06 4:46 ` Mike Frysinger
2015-10-17 10:07 ` Anthony G. Basile
2015-10-22 13:57 ` Mike Frysinger
2015-12-20 21:31 ` Mike Gilbert
2015-10-29 21:18 ` [gentoo-dev] moving gcc-5.2 to unstable Mike Frysinger
2015-12-09 4:28 ` [gentoo-dev] moving gcc-5.3 " Mike Frysinger
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=20151002022109.1f211ef9@caribou.gateway.pace.com \
--to=rhill@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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