Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 167701 - Document known problems with gcc upgrades
Summary: Document known problems with gcc upgrades
Status: RESOLVED WONTFIX
Alias: None
Product: [OLD] Docs on www.gentoo.org
Classification: Unclassified
Component: Other documents (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Docs Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-20 00:19 UTC by Dustin J. Mitchell
Modified: 2007-02-21 19:05 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dustin J. Mitchell 2007-02-20 00:19:24 UTC
Given the vast number of duplicate bugs on bug #64615, could I propose an update to http://www.gentoo.org/doc/en/gcc-upgrading.xml?  In particular, comment #120 would be helpful.

Comment #93 directs me to look at gcc-upgrading.xml and learn that I must unmerge the old gcc before trying to emerge world.  I see nothing to that effect, but I do see "It is safe to remove the older GCC version at this time. If you feel the need...", but that's not quite a "YOU MUST" kind of statement..

I'm not entirely clear on what the answers in the ticket are, so I can't write a patch to the documentation just yet.  I was hoping some of the folks that had worked on that ticket could help, but they seem pretty grumpy.
Comment 1 Xavier Neys (RETIRED) gentoo-dev 2007-02-20 00:35:24 UTC
"If you feel the need..." is right.
You'll want to keep the old version if you still need it, e.g. to compile quem
Comment 2 Dustin J. Mitchell 2007-02-20 00:57:07 UTC
Bug #64615 indicates it's not right, and in fact, that the world emerge will break without removing the old gcc.  My experience matches this, as presumably does that of all the folks whose bugs have been dupe'd to 64615.

This isn't really a good situation, here.  I was yelled at on 64615 for asking for clarification (and offering to submit a doc patch with my newly attained clarity).  Now on the documentation ticket I'm told that the information from ticket 64615 was incorrect.  What's up?
Comment 3 SpanKY gentoo-dev 2007-02-20 02:45:10 UTC
well the statement is incorrect ... you do not need to unmerge any version of gcc, you simply need to rebuild all the applications that were using the old C++ lib
Comment 4 Jan Kundrát (RETIRED) gentoo-dev 2007-02-21 19:05:19 UTC
(In reply to comment #2)
> This isn't really a good situation, here.  I was yelled at on 64615 for asking

You weren't yelled at, you've been asked not to reopen that bug because it makes the developers that it's assigned to nervous and doesn't reflect how we work with Bugzilla. It wasn't your fault, so Carsten pointed out you shouldn't do that.

> for clarification (and offering to submit a doc patch with my newly attained
> clarity).  Now on the documentation ticket I'm told that the information from
> ticket 64615 was incorrect.  What's up?

The two comments you're referring to are from two users. There's no guarantee that they are correct. Our database is publicly accessible and anyone can post comments, so you shouldn't take everything for granted.

Anyway, I can't find anything else besides "ask users to remove their old GCC" in your request, and that point is -- as vapier said -- wrong. Thanks for your effort anyway :)