On 2011-06-14 13:06, Adam Borowski wrote:
> 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
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-multi
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.
Thanks for the bug report! I'm afraid I don't understand i
Package: ccache
Version: 3.1.5-1
Severity: important
Hi!
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.
I see that the symlinks in /usr/lib/ccache are
4 matches
Mail list logo
