public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: toolchain update was Re: [gentoo-project] Re: Questions for candidates for Gentoo Council 2013/2014
Date: Sat, 6 Jul 2013 09:39:07 -0700	[thread overview]
Message-ID: <CAEdQ38FpEF1nw_aL3MR-SOQTtcnJsq9oiqVf+nxp5vMMejqujw@mail.gmail.com> (raw)
In-Reply-To: <51D83798.4000306@gentoo.org>

On Sat, Jul 6, 2013 at 8:28 AM, Rick "Zero_Chaos" Farina
<zerochaos@gentoo.org> wrote:
> You are misremembering that we are using preserve_libs to save our butts
> when mpc is updated and gcc is still linked to the old mpc.  I feel very
> uncomfortable as the recommendation of preserve-libs is to remerge as
> soon as possible not "build a whole system like this".  Is there an
> actual failure here? Not that I've seen yet, but it's an awkward way to
> build in my opinion.

Keeping the old libs seems perfectly fine, since it's in a seed stage
that we don't care about after stage1 is complete.

An unnecessary build of gcc may not matter much on a relatively fast
amd64, but it's going to be a pain on a bunch of slower architectures.
And on mips/multilib it'll be even worse since we get to build the
libraries for three ABIs.


  reply	other threads:[~2013-07-06 16:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201307012054.06728.Arfrever.FTA@gmail.com>
     [not found] ` <51D2CB89.9050402@opensource.dyc.edu>
     [not found]   ` <20130702234246.05507806@caribou.gateway.2wire.net>
     [not found]     ` <51D722BC.10207@gentoo.org>
     [not found]       ` <20130705194108.08a46f2f@caribou.gateway.2wire.net>
     [not found]         ` <51D77E8A.1070108@gentoo.org>
2013-07-06  4:27           ` [gentoo-dev] Re: toolchain update was Re: [gentoo-project] Re: Questions for candidates for Gentoo Council 2013/2014 Brian Dolbec
2013-07-06  5:16             ` Ryan Hill
2013-07-11  2:03             ` Robin H. Johnson
2013-07-11  3:36               ` Rick "Zero_Chaos" Farina
2013-07-11  3:42                 ` Matt Turner
2013-07-11  3:43                 ` Robin H. Johnson
2013-07-11  3:58                   ` Zac Medico
2013-07-06  7:08           ` Matt Turner
2013-07-06  7:46             ` Brian Dolbec
2013-07-06 16:36               ` Matt Turner
2013-07-06 17:33                 ` Brian Dolbec
2013-07-06 15:28             ` Rick "Zero_Chaos" Farina
2013-07-06 16:39               ` Matt Turner [this message]
2013-07-06 18:37                 ` Anthony G. Basile

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=CAEdQ38FpEF1nw_aL3MR-SOQTtcnJsq9oiqVf+nxp5vMMejqujw@mail.gmail.com \
    --to=mattst88@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