On 07/06/2013 12:39 PM, Matt Turner wrote:
On Sat, Jul 6, 2013 at 8:28 AM, Rick "Zero_Chaos" Farina
<[email protected]> 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.
Thanks Matt, I was going to make that point. ~3 days to recompile world
on the lemote yeelong.
--
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197
