Re: 32-rc1: "CROSS_COMPILE changed" message breaks compilation

[Sam Ravnborg]

On Sat, Oct 17, 2009 at 08:25:12PM +0200, Pavel Machek wrote:
> On Sun 2009-10-11 23:27:57, Sam Ravnborg wrote:
> > On Mon, Sep 28, 2009 at 09:25:36PM +0200, Pavel Machek wrote:
> > > Hi!
> > > 
> > > > > After update to 2.6.32-rc1, I'm getting
> > > > > 
> > > > > "Makefile:197: *** CROSS_COMPILE changed from "ccache" to to "ccache ". Use "make mrproper" to fix it up. Stop.
> > > > > 
> > > > > Note that the message has typo in it ("to to")... What is worse, the
> > > > > message triggers even when I try to run make mrproper. Ouch.
> > > > 
> > > > The massage is changed in kbuild-fixes.git - but it addresses only ARCH=
> > > > 
> > > > As a followup to your other mails:
> > > > The reason to use "make mrproper" is that when ARCH or CROSS_COMPILE changes
> > > > you have generally either decided to build for a new architecture or
> > > > you have changed the way you build the kernel (new toolchain or whatever).
> > > > So to clean up using "make mrproper" is perfectly justified.
> > > > 
> > > > The target group that uses CROSS_COMPILE to enable ccache are using
> > > > CROSS_COMPILE is a way it is not designed for so they should expect that it
> > > > is not a perfect match.
> > > 
> > > What is the recommended way to run ccache, then?
> > ccache is a frontend to gcc - so I would have expected
> > you would use: 
> > 
> >     make CC="ccache gcc"
> > 
> > Or does ccache also benefit ld and as and the other that receive
> > the $(CROSS_COMPILE) prefix?
> 
> You are right that I don't strictly need ccache for anything but cc.
> 
> But anyway, check was buggy; I had CROSS_COMPILE="ccache ", and the
> space at the end broke it.

I assume you did not read the other mail relevant to this topic.
The patch in question has been reverted.

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/