From: Tomas Mozes <hydrapolic@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: stable gcc 5.4.0 ??
Date: Thu, 20 Apr 2017 07:36:03 +0200 [thread overview]
Message-ID: <CAG6MAzSr7fkXTM+EHqwn56ZCUSwYM_NAHKuTDbKHzUpQ0FKcGQ@mail.gmail.com> (raw)
In-Reply-To: <20170419182551.GB19805@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
On Wed, Apr 19, 2017 at 8:25 PM, Walter Dnes <waltdnes@waltdnes.org> wrote:
> > It is stable. Even there are open bugs, arches started stabilizing it.
>
> Is gcc-5.4.0 built "--with-default-libstdcxx-abi=gcc4-compatible"?
> On the Pale Moon linux sub-forum, there were crashing issues with the
> contributed Ubuntu build when Ubuntu switched to gcc 5. The maintainer
> of the Ubuntu Pale Moon build had to drop back to gcc 4.9 to fix the
> crashes.
>
> At home, for personal use, I build Pale Moon with a manually built
> version of gcc 5.4.0. Pale Moon has been rock solid for me on Gentoo
> and on a refurbished Lenovo T400 running Puppy Linux. The option
> "--with-default-libstdcxx-abi=gcc4-compatible" may be the reason it
> works for me.
>
> This may be valid for other applications, too. I think the problem is
> that you need the entire system to be one of...
>
> "--with-default-libstdcxx-abi=new" or
>
> "--with-default-libstdcxx-abi=gcc4-compatible"
>
> Mixing together does not seem to work.
>
> --
> Walter Dnes <waltdnes@waltdnes.org>
> I don't run "desktop environments"; I run useful applications
>
>
The default is new:
https://www.gentoo.org/support/news-items/2015-10-22-gcc-5-new-c++11-abi.html
[-- Attachment #2: Type: text/html, Size: 1987 bytes --]
next prev parent reply other threads:[~2017-04-20 5:36 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 [this message]
2017-04-20 22:17 ` Walter Dnes
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=CAG6MAzSr7fkXTM+EHqwn56ZCUSwYM_NAHKuTDbKHzUpQ0FKcGQ@mail.gmail.com \
--to=hydrapolic@gmail.com \
--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