On Mon, Jun 13, 2011 at 10:12:20PM +0200, Joel Rosdahl wrote:
> On 2011-06-13 12:02, Adam Borowski wrote:
> > I'm afraid that ccache will break compilation of anything that specifies the
> > full name of the compiler ("x86_64-linux-gnu-gcc" rather than "gcc"). It
> > does still work with non-multiarch ones.
>
> Does ccache actually break compilation? If so, in what way?
For an actual break, you'd need a more complex setup with extra layers like
colorgcc or distcc, and in that case it might be argued to be an user
configuration error (except that there's no proper configuration in such
cases other than creating the symlink yourself).
But even when ccache is used by itself, it will "merely" not work.
> Or is the problem that ccache doesn't correctly create symlinks in
> /usr/lib/ccache anymore so that some compilers will not be invoked via
> ccache (if the user has /usr/lib/ccache the path)?
Yeah. If you want to ever use distcc when the server might be on a
different architecture, you need to invoke $(gcc -dumpmachine)-gcc.
The current version of ccache will handle plain "gcc" but not one with
explicitely specified architecture.
> What package should I install and
> what should I do to reproduce the problem?
ccache and recent gcc.
Try to run "x86_64-linux-gnu-gcc" -> no ccache.
--
1KB // Microsoft corollary to Hanlon's razor:
// Never attribute to stupidity what can be
// adequately explained by malice.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
