-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/06/2013 03:08 AM, Matt Turner wrote: > On Fri, Jul 5, 2013 at 7:18 PM, Rick "Zero_Chaos" Farina > <zeroch...@gentoo.org> wrote: >> When we then move onto stage 2, it uses just the packages built during >> stage1 (/tmp/stage1root becomes /). This means, if seed stage has >> mpc.so.0.1 but portage has since included mpc.so.2 that the gcc in >> stage2 is linked against mpc.so.0.1 but only mpc.so.0.2 is installed. >> >> To combat this kind of failure we are currently running "emerge --update >> - --deep --newuse --complete-graph --rebuild-if-new-ver gcc" which could >> just be "emerge --update gcc" if eapi 5 subslots were used properly. > > The best solution to this is, and has always been, just updating gcc's > deps during update_seed. Or am I misremembering something?
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. - -Zero > > As far as I know, you don't need to waste time rebuilding the seed > stage's gcc, since gcc is rebuilt in stage2 and then everything is > built by it in stage3. > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJR2DeYAAoJEKXdFCfdEflKDwwP/1Pr2eB9GjSKncEabiB9WkEb eziSaccKcsmjdXq9Svg0dfTM9m9rgroK0iM15IWLHhbAoU/5beVPv4bOYVYejYkP NBMWp2+MoIE7VRhziFToj7tHxTnXsUg1l3dMFWECewWpMewo9lZw1eYTn/iaUGaI tkfNi7iQV9PvfknUgtQZ8lfgSUjUz2CdtjCyjaoMpO+vls+gVvH74vGETIMMrHWr CN7iMfx7F6FGpc1+FxZ0CJ1zKSifY/1R+dLABass8xaLRMPNqTIpm8b37xD2tHOA f2pfzCIgkwLEo8moJrmkl21CqC2CjqZ0HPqd3dd/wSTg2x1ccslNHVOUf8+mZu1I 4zwJUwS7e2w8rxcq/UTu9x3J18D2doFjLg1mLUtWgmptn9Tydr/GYL+yYJei0yK+ MiADpdK+UI5frUo1B8bZ+Gs0N5IIh2pcGkjdupz4HXRAeD+2VN5G0HBpTZ8I4vNI rK9wRQN1iyxb4sn0Wr0n+GwSlxyTao6yuUSJwT5nfD1k9gSGI9Zh7tERlD/D9ceN Vfvv0No+ikh47TDjm3hSmz2fdbTT5vxKecnXT72EpYQwIZFoVMo7tnRVwxd4gBbM Fx4LDUaSn3ommMBZF/jRt5zsn+cGMB/7qHkNo1DPIbKgXgExEQWRz7Lxhy8Hm4er YYVhPl4Zhc0/BCBwBpK/ =zakW -----END PGP SIGNATURE-----
