In the last time, gcc was updated to rev 7 and the ebuild deletes the symlink to /usr/bin/${CHOST}-g++. (Should be for downgrading from gcc 3) The deletion of this symlink causes that some ebuilds can't compile (Like kde 3.0.2, STL not found bug) Workaround: ln -s /usr/bin/g++ /usr/bin/${CHOST}-g++
Ok, only problem I have, is that gcc-2.95.3 do not have a ${CHOST}-g++.
Look in the ebuild.... pkg_preinst() { # downgrading from gcc-3.x will leave this symlink, so # remove it. resolves bug #3527 if [ -L ${ROOT}/usr/bin/${CHOST}-g++ ] then rm -f ${ROOT}/usr/bin/${CHOST}-g++ fi } when you have a ${CHOST} of i686-pc-linux-gnu then, the symlink should be /usr/bin/i686-pc-linux-gnu-g++ -> /usr/bin/g++ I hope you understand me now... Roman
Ok, let me put it this way. If you have a new 1.2 system, which only have gcc-2.95.3 installed, you do *NOT* have a /usr/bin/$CHOST-g++ ! Why that code was added, is because some users installed gcc-3.x, which *DO* install /usr/bin/$CHOST-g++ if it is not a parallel install. If they then downgrade back to 2.95.3, the /usr/bin/$CHOST-g++ which is still from gcc-3.x, do not get removed. So basically, if kde do not compile without /usr/bin/$CHOST-g++, then it is either a bug in kde, or in gcc-2.95.3 (for not installing /usr/bin/$CHOST-g++ in the first place). To prove my point, install gentoolkit, and do something like: # epm -ql gcc-2.95.3-r7 |grep $CHOST-g\+\+ (make sure CHOST is actually set) You will not get any output as it was never installed. Also, note that because that code that removes $CHOST-g++ is in pkg_preinst(), it removes the file from the live filesystem, and not from $D, which just confirms that it never existed if you look at the output from epm. Now, do not understand me wrong ... if it being missing is a bug in gcc, then sure, we should fix it. If it however is a problem with kde, or your installation, then whatever should rather be fixed.
I started with a 1.0 system.... And as I remember, i had to lay this symlink 2 times in the last months.... (Not only for kde, for another package, but don't ask...) And i'm not alone with this issue......(Look in the dev-archive Subject: [gentoo-dev] KDE 3.02 Build Problem) I don't know, if it's a gcc or kde issue..... After grepping the config log of kde it assumed that i686-pc-linux-gnu-g++ was not found....(And I remembered, I had this problem not the first time) And it's a working workaround for me.... Sorry for the misunderstandings....
Fixed....See Announcement
Yep, weird one. Used to work without .. even did so the other day that I tested gcc (remerged whole system). Oh well, *shrug* :)
The deep miracles of GCC, KDE, autoconf and all other involved programs...;-)
