Gentoo Archives: gentoo-dev

From: "Rick \\\"Zero_Chaos\\\" Farina" <zerochaos@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: toolchain update was Re: [gentoo-project] Re: Questions for candidates for Gentoo Council 2013/2014
Date: Sat, 06 Jul 2013 15:28:33
Message-Id: 51D83798.4000306@gentoo.org
In Reply to: [gentoo-dev] Re: toolchain update was Re: [gentoo-project] Re: Questions for candidates for Gentoo Council 2013/2014 by Matt Turner
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 On 07/06/2013 03:08 AM, Matt Turner wrote:
5 > On Fri, Jul 5, 2013 at 7:18 PM, Rick "Zero_Chaos" Farina
6 > <zerochaos@g.o> wrote:
7 >> When we then move onto stage 2, it uses just the packages built during
8 >> stage1 (/tmp/stage1root becomes /). This means, if seed stage has
9 >> mpc.so.0.1 but portage has since included mpc.so.2 that the gcc in
10 >> stage2 is linked against mpc.so.0.1 but only mpc.so.0.2 is installed.
11 >>
12 >> To combat this kind of failure we are currently running "emerge --update
13 >> - --deep --newuse --complete-graph --rebuild-if-new-ver gcc" which could
14 >> just be "emerge --update gcc" if eapi 5 subslots were used properly.
15 >
16 > The best solution to this is, and has always been, just updating gcc's
17 > deps during update_seed. Or am I misremembering something?
18
19 You are misremembering that we are using preserve_libs to save our butts
20 when mpc is updated and gcc is still linked to the old mpc. I feel very
21 uncomfortable as the recommendation of preserve-libs is to remerge as
22 soon as possible not "build a whole system like this". Is there an
23 actual failure here? Not that I've seen yet, but it's an awkward way to
24 build in my opinion.
25
26 - -Zero
27 >
28 > As far as I know, you don't need to waste time rebuilding the seed
29 > stage's gcc, since gcc is rebuilt in stage2 and then everything is
30 > built by it in stage3.
31 >
32 >
33
34 -----BEGIN PGP SIGNATURE-----
35 Version: GnuPG v2.0.19 (GNU/Linux)
36 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
37
38 iQIcBAEBAgAGBQJR2DeYAAoJEKXdFCfdEflKDwwP/1Pr2eB9GjSKncEabiB9WkEb
39 eziSaccKcsmjdXq9Svg0dfTM9m9rgroK0iM15IWLHhbAoU/5beVPv4bOYVYejYkP
40 NBMWp2+MoIE7VRhziFToj7tHxTnXsUg1l3dMFWECewWpMewo9lZw1eYTn/iaUGaI
41 tkfNi7iQV9PvfknUgtQZ8lfgSUjUz2CdtjCyjaoMpO+vls+gVvH74vGETIMMrHWr
42 CN7iMfx7F6FGpc1+FxZ0CJ1zKSifY/1R+dLABass8xaLRMPNqTIpm8b37xD2tHOA
43 f2pfzCIgkwLEo8moJrmkl21CqC2CjqZ0HPqd3dd/wSTg2x1ccslNHVOUf8+mZu1I
44 4zwJUwS7e2w8rxcq/UTu9x3J18D2doFjLg1mLUtWgmptn9Tydr/GYL+yYJei0yK+
45 MiADpdK+UI5frUo1B8bZ+Gs0N5IIh2pcGkjdupz4HXRAeD+2VN5G0HBpTZ8I4vNI
46 rK9wRQN1iyxb4sn0Wr0n+GwSlxyTao6yuUSJwT5nfD1k9gSGI9Zh7tERlD/D9ceN
47 Vfvv0No+ikh47TDjm3hSmz2fdbTT5vxKecnXT72EpYQwIZFoVMo7tnRVwxd4gBbM
48 Fx4LDUaSn3ommMBZF/jRt5zsn+cGMB/7qHkNo1DPIbKgXgExEQWRz7Lxhy8Hm4er
49 YYVhPl4Zhc0/BCBwBpK/
50 =zakW
51 -----END PGP SIGNATURE-----

Replies