From: Pavel Machek <pavel@ucw.cz>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: kernel list <linux-kernel@vger.kernel.org>, linux-kbuild@vger.kernel.org
Subject: Re: 32-rc1: "CROSS_COMPILE changed" message breaks compilation
Date: Sat, 17 Oct 2009 20:25:12 +0200 [thread overview]
Message-ID: <20091017182511.GC16532@elf.ucw.cz> (raw)
In-Reply-To: <20091011212757.GA2768@merkur.ravnborg.org>
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.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-10-17 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 17:56 32-rc1: "CROSS_COMPILE changed" message breaks compilation Pavel Machek
2009-09-28 18:03 ` Pavel Machek
2009-09-28 18:08 ` Pavel Machek
2009-09-28 19:08 ` Sam Ravnborg
2009-09-28 19:24 ` Pavel Machek
2009-09-28 19:25 ` Pavel Machek
2009-09-28 22:22 ` Bernd Petrovitsch
2009-10-11 21:27 ` Sam Ravnborg
2009-10-17 18:25 ` Pavel Machek [this message]
2009-10-17 18:41 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091017182511.GC16532@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox