ccache was on my system for a while but I decided to unmerge it and remove all references to it. Now when I compile libbonobo-2.0.1, I get a strange ccache error as described in the attachment provided. The issued command is: "CC=/usr/bin/gcc CXX=/usr/bin/g++ emerge -u libbonobo". I couldn't find the solution to this. Mark
Created attachment 5388 [details] Output of the error
How did you remove 'all references to it' ? be a bit more verbose please. Try remove and emerge ORBit2 again.
Hello Foser, From what I can recall, I removed /usr/bin/ccache, /root/.ccache, I changed the CC-variable from "ccache gcc" to "gcc" and removed a reference in my path (/etc/profile). grep -r ccache /etc/* yields no results.
As an addition; I just saw the re-emerge of ORBit2 erroring out the same way.
You removed /usr/bin/ccache ? Did you do an 'emerge -C ccache' ?
Yes, but /usr/bin/ccache had to be removed automatically. It wasn't a big deal there were just a bunch of dead symlinks in there.
Hmm seems strange to me.. it should remove _all_ traces, except maybe for some config files (and .ccache files, but those won't hurt). It looks to me as if orbit-idl-2 tries to use ccache for some reason, but i'm not sure 'sh: line 1: ccache: command not found Error: Empty file' refers to that. You have ccache disabled in //etc/make.globals FEATURES (it shouldn't be in the string)?
FEATURES in /etc/make.globals contains FEATURES="sandbox". grep -r ccache /usr/portage also doesn't yield usuable results... I'm out of clues certainly :(
Foser: Got any idea what the issue might be?
It was solved by doing "emerge libIDL". Maybe it should be an option that whenever ORBit2 is recompiled, it will first remerge libIDL? Summary: When libIDL is compiled (in my case by ccache gcc) but the compiler is changed (or removed), ORBit2 will not compile anymore. Re-emerging libIDL will solve this case.
Hmm i thought it was something like that, just didn't think of libIDL (got close with ORBit2 ;)). We cannot force recompilation of deps in an ebuild (and im not sure we should). I think this was a rare condition and its good you figured it out so we can think of it next time ;) Not much we can do about it.
Alright, thanks Foser :)
