public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Barry Schwartz <chemoelectric@chemoelectric.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Status of Gcc-5.1.0?
Date: Sat, 23 May 2015 15:36:13 -0500	[thread overview]
Message-ID: <20150523203613.GA4042@crud> (raw)
In-Reply-To: <20150523124802.6bd085304b87689bdcb13b4c@comcast.net>

Frank Peters <frank.peters@comcast.net> skribis:
> On Sat, 23 May 2015 15:47:04 +0000 (UTC)
> Martin Vaeth <martin@mvath.de> wrote:
> 
> > 
> > My experience is quite the opposite: With graphite, I had
> > many random crashes (and seldom also unexplainable compiler
> > errors which vanish without graphite).
> >
> 
> My whole system has been compiled with graphite since its introduction
> and I've never seen any problems.

Well, to my mind, the biggest problem with graphite is how it is
dependent on libraries with funny names. Thus one should always, I
think, at least keep a compiler of _some_ reliable version around
compiled without it, and capable of building other gcc versions.

I tend to keep quite a few gcc versions around, but then I like to
program and occasionally to test on different versions. Also, being
conservative, I generally use a newer version for development than for
building my system. I do not move my system compiler to a new version
just because I installed that version. One can always set the compiler
per-package via /etc/portage files.


  reply	other threads:[~2015-05-23 20:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 18:55 [gentoo-amd64] Status of Gcc-5.1.0? Frank Peters
2015-05-22 18:35 ` Stefan G. Weichinger
2015-05-22 21:41   ` Frank Peters
2015-05-23 15:47     ` [gentoo-amd64] " Martin Vaeth
2015-05-23 16:48       ` Frank Peters
2015-05-23 20:36         ` Barry Schwartz [this message]
2015-05-25 12:29         ` Martin Vaeth

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=20150523203613.GA4042@crud \
    --to=chemoelectric@chemoelectric.org \
    --cc=gentoo-amd64@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