using ccache breaks arts (kde ) build

johnboyd · n00b Joined: 07 Jun 2002 Posts: 15

using ccache seems to confuse arts-1.0.1.20020604.ebuild. the configure process reports that no STL is found. However, when I unmerge ccache the configure scripts find the real g++ and this solves the problem.

Do the symlinks that ccache creates somehow confuse the configure test process? Or something else? With ccache enabled, the configure reports that the name of the symlink as the c++ compiler (which points to ccache). I think ccache is not working correctly? Is there a simple way to resolve this problem? Otherwise, ccache is a great idea.

fghellar · Posted: Wed Jul 03, 2002 12:21 am Post subject:

Hi! Have you followed this thread? Which version of Portage are you using?

ebuild /usr/portage/kde-base/arts/arts-1.0.1.20020604.ebuild compile works fine for me, with portage-2.0.4.
_________________
| www.gentoo.org | www.tldp.org | www.google.com |

johnboyd · n00b Joined: 07 Jun 2002 Posts: 15

There are several default long symlinks in the
ccache directory:

i686-pc-linux-gnu-gcc
i686-pc-linux-gnu-g++

etc. These are what confuse the
configure script. If they are removed, then:

g++
gcc

the shorter synlinks are found first.
and the compile proceeds normally. Don't
ask me why, but deleting the longer
symlink seems to solve the problem.

fghellar · Posted: Wed Jul 03, 2002 9:02 pm Post subject:

Well, you didn't answer, so I'll have to ask again if you read that thread, esp. my post with an "Important Update" on Thu Jun 27, 2002... Please come back with any info...
_________________
| www.gentoo.org | www.tldp.org | www.google.com |

johnboyd · n00b Joined: 07 Jun 2002 Posts: 15

Sorry, but that thread is irrelevant to my post. I am not getting any permission errors. The error returned by the arts (the first dependancie in the kde build) configure script
is

configure: error: "no known STL type found - did you forget to install libstdc++-devel ?"

no I didn't forget. when I unmerge ccache all is well and everything compiles normally. The name of the compiler is then referred to as "g++" and not the symlink that ccache sets up.

Changing the ccache directory has no effect. I might revert to older portage... thanks for your help

fghellar · Posted: Sat Jul 06, 2002 5:04 am Post subject:

Maybe it's related to this one, then...
_________________
| www.gentoo.org | www.tldp.org | www.google.com |

johnboyd · n00b Joined: 07 Jun 2002 Posts: 15

Thanks for the reply, I edited my earlier post to say that deleting
the links that included the ${chost} attachment to g++ made things work again.

I wonder why the longer symlinks are even necessary? Is it because
ccache needs to include them in the hash it creates?

hielvc · Posted: Sat Sep 14, 2002 12:50 am Post subject:

Well just a note for historical records the ccache long links bug is still around and kickin even with gcc3.2. Followed the above and deleted the long links in /usr/bin/ccache and arts is now building. Dont know exactly why I need it as I dont use KDE but "emerge -u world" says Is needs it, sigh.

hielvc