Summary: | cdk Ebuild (5.0.20050424) refrences gcc 3.4.3 libs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stephen Lecheler <salin> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | log from a failed attempt to "emerge cdk" |
Description
Stephen Lecheler
2005-11-24 19:51:05 UTC
Created attachment 73542 [details]
log from a failed attempt to "emerge cdk"
fix_libtool_files.sh 3.4.3 *** This bug has been marked as a duplicate of 73435 *** Attempted the fix in the refrenced bugreport. No go. After the fix "fix_libtool_files.sh 3.4.3" emerging cdk still throws the error. The provided solution is not correct. re-emerge libtool then... *** This bug has been marked as a duplicate of 73435 *** This has been verified as a sucessful way to fix the problem. Why does the emerge system not automatically do this? (In reply to comment #5) > This has been verified as a sucessful way to fix the problem. > > Why does the emerge system not automatically do this? fix_libtool_files.sh *is* run automatically after upgrading gcc. For some weird reason, it's sometimes not enough to fix the hardcoded paths (and you cannot run emerge from within emerge to re-emerge libtool). Thanks for reporting back, closing. |