Summary: | Emerging jpeg-6b-r4 fails while linking due to ebuild gettin wrong version info for gcc | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Evan Borgstrom <evan> |
Component: | [OLD] Library | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | fly-a-lot |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Evan Borgstrom
2005-02-10 10:35:26 UTC
re-emerge libtool *** This bug has been marked as a duplicate of 80424 *** *** Bug 87105 has been marked as a duplicate of this bug. *** The scheme to solve the problem (at least for me) has been described in http://bugs.gentoo.org/show_bug.cgi?id=80424#c2 In my case it wasn't neccessary to touch /etc/env.d/05gcc since it was o.k. Reemerging libtool seems to be the key to solve the problem. However, in case doing this won't do the trick for you I need to tell you I did a little more than that: Before I was directed to this solution I did a brute force grep to find any hard coded "i686-pc-linux-gnu/3.3.4" on my system. So I already found and changed file /usr/X11R6/bin/libtool (well this was the only relevant file grep found so far, but grep didn't finish yet). In this file I changed 4 to 5 'i686-pc-linux-gnu/3.3.4' to 'i686-pc-linux-gnu/3.3.5'. However, I'm not sure if this makes any difference since I reemerged libtool later. Just wanted to let anybody know in case reemerging libtool alone and checking the /etc/env.d/05gcc file don't help to solve the problem for you. |