Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 77835 - GCC upgrades can cause compiling troubles
Summary: GCC upgrades can cause compiling troubles
Status: RESOLVED DUPLICATE of bug 73435
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All All
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-13 07:19 UTC by Rene Androsch
Modified: 2005-07-17 13:06 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 Rene Androsch 2005-01-13 07:19:11 UTC
Again and again and again - its always the same.
After doing an gcc upgrade (in this case 3.3.4 -> 3.3.5) I'm unable to compile anything afterwards.

After again, searching in the bug tracker, I find the solution: "run fix_libtool_files.sh <old_gcc_version>".

It is annoying, because the gcc ebuilds DO NOT tell you, that you have to run this script - I check my logfiles in /var/log/portage/* !

It would be great, if the gcc ebuilds would honor this, or at least gcc-config, which is actually used to switch between gcc versions! I hope that this gets somehow automated, or I see myself and others again searching the bugtracker after the "libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/<old_gcc_version>/libstdc++.la' is not a valid libtool archive" error ...
Comment 1 Rene Androsch 2005-01-13 07:21:11 UTC
BTW the bug 51922 and 64519 are open, because of this exact behaviour! I think that automating the "fix_libtool_files.sh" step after an gcc upgrade, will at least help to lower related sounding bug reports!
Comment 2 Carsten Lohrke (RETIRED) gentoo-dev 2005-01-13 07:28:14 UTC
*** This bug has been marked as a duplicate of 73435 ***

*** This bug has been marked as a duplicate of 73435 ***