From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: stable gcc 5.4.0 ??
Date: Thu, 20 Apr 2017 18:17:53 -0400 [thread overview]
Message-ID: <20170420221753.GB28261@waltdnes.org> (raw)
In-Reply-To: <CAG6MAzSr7fkXTM+EHqwn56ZCUSwYM_NAHKuTDbKHzUpQ0FKcGQ@mail.gmail.com>
On Thu, Apr 20, 2017 at 07:36:03AM +0200, Tomas Mozes wrote
>
> The default is new:
> https://www.gentoo.org/support/news-items/2015-10-22-gcc-5-new-c++11-abi.html
And the news item says...
> Display-If-Installed: >=sys-devel/gcc-5
...which means that people like me, who currently have 4.9.4, won't know
about it until after the fact. Then they'd have to...
[i660][waltdnes][~] emerge -pve @world
Total: 529 packages (3 upgrades, 526 reinstalls), Size of downloads: 10,360 KiB
...fun !NOT. If you're doing a fresh install, ***WITH A GCC5-BUILT
INSTALL CD AND STAGE 3***, then yes, go for it. But changing horses in
mid-stream can be painfull. Would it hurt to stay with 4.9.4 for the
time being, assuming that you're not using prebuilt stuff like
firefox-bin or libreoffice-bin? What would be the best way to go about
it?
A) Would 5.4.0 be slotted separately, and 4.9.4 left as the default?
B) Add "-D_GLIBCXX_USE_CXX11_ABI=0" to CFLAGS and CXXFLAGS
C) Mask out ">sys-devel/gcc-4.99"
D) Allow "--with-default-libstdcxx-abi=gcc4-compatible" via a USE flag?
Whatever option is selected, people need to be warned about it *NOW*,
not after gcc-5.4.0 has been installed. I wonder if it's going to be
worth it to go to 5.4. Looking at https://gcc.gnu.org/ today, I see...
GCC 5.4 Status: 2016-06-03 (regression fixes & docs only).
GCC 6.3 Status: 2016-12-21 (regression fixes & docs only).
GCC 7.1 Status: 2017-04-20 (frozen, all changes require RM approval).
Development: GCC 8.0 Status: 2017-04-20 (regression fixes & docs only).
Maybe we should what many enterprises do with Windows; i.e. skip a
version and go straight to gcc-6.
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2017-04-20 22:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 8:15 [gentoo-dev] stable gcc 5.4.0 ?? Jörg Schaible
2017-04-18 8:37 ` Tomas Mozes
2017-04-18 9:16 ` [gentoo-dev] " Jörg Schaible
2017-04-18 9:44 ` Mart Raudsepp
2017-04-18 11:07 ` M. J. Everitt
2017-04-18 12:44 ` Tomas Mozes
2017-04-18 13:12 ` [gentoo-dev] " Jörg Schaible
2017-04-18 13:27 ` James Le Cuirot
2017-04-18 13:38 ` Aaron W. Swenson
2017-04-18 14:12 ` [gentoo-dev] " Jörg Schaible
2017-04-18 14:40 ` [gentoo-dev] " Tomas Mozes
2017-04-18 14:41 ` [gentoo-dev] " Tomas Mozes
2017-04-19 7:31 ` [gentoo-dev] " Jörg Schaible
2017-04-19 9:22 ` Tomas Mozes
2017-04-19 18:25 ` Walter Dnes
2017-04-20 5:36 ` Tomas Mozes
2017-04-20 22:17 ` Walter Dnes [this message]
2017-04-20 22:51 ` Mart Raudsepp
2017-04-20 22:52 ` Matthias Maier
2017-04-21 1:44 ` Walter Dnes
2017-04-21 16:21 ` [gentoo-dev] " Jörg Schaible
2017-04-21 19:29 ` Francesco Riosa
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=20170420221753.GB28261@waltdnes.org \
--to=waltdnes@waltdnes.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