On Fri, Aug 14, 2009 at 04:29:17PM -0700, walt wrote:
> On 08/14/2009 04:17 PM, [email protected] wrote:
> > Are any special steps needed to handle this upgrade, other than using
> > gcc-config to change the current selection? Do I need to follow the
> > upgrade docs, such as remergeing system and world?
>
> I'm no expert, but I just did the same upgrade this morning, and all I
> did was run fix_libtool_files afterward. So far, no problems.
>
> The really nasty upgrade is when the version of libstdc++ changes, which
> it hasn't lately, and then you need to recompile every app that uses it.
Right, but the upgrade guide specifically mentions
If you install a new major version of GCC (such as 3.3.6 to 3.4.5),
the system will not switch over to use it automatically. You'll
have to explicitly request the change because the migration process
might require some additional steps. If you decide not to switch,
Portage will continue to use older version of your compiler until
you change your mind, or remove the old compiler from the system.
Non-major gcc upgrades are switched automatically for you (such as
3.4.5 to 3.4.6).
This being 4.3.4 to 4.1.1 looks like a major version change according
to the upgrade guide. It doesn't mention what a switch manual takes,
but it does list a whole series of steps such as remerging system and
world without saying exactly when they or how much are necessary. I'd
just as soon not do that unless necessary, but I'd much more regret
not doing it if I should have.
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / [email protected]
GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
