From: Adrian Bunk <bunk@stusta.de>
To: Kalin KOZHUHAROV <kalin@thinrope.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Howto set kernel makefile to use particular gcc
Date: Sun, 1 Jan 2006 13:00:57 +0100 [thread overview]
Message-ID: <20060101120057.GS3811@stusta.de> (raw)
In-Reply-To: <dp89d4$u0i$1@sea.gmane.org>
On Sun, Jan 01, 2006 at 07:03:15PM +0900, Kalin KOZHUHAROV wrote:
>
> As I just stumbeled into a similar problem, I am going to ask here.
>
> I know the "trick" of `make -j8 CC=distcc` and I always use it. But is there a way to hardwire
> "CC=distcc" insie the Makefile? Just setting it there does not help it seems.
Setting it somewhere at the top of the Makefile doesn't help since the
Makefile sets it itself later overriding your setting.
The Makefile contains the line
CC = $(CROSS_COMPILE)gcc
Change this line to
CC = $(CROSS_COMPILE)distcc
> Kalin.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-01-01 12:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 7:04 Howto set kernel makefile to use particular gcc Mukund JB.
2005-12-30 7:24 ` Chris White
2006-01-01 10:03 ` Kalin KOZHUHAROV
2006-01-01 11:13 ` Marc Giger
2006-01-01 11:18 ` Keith Owens
2006-01-01 11:37 ` Marc Giger
2006-01-01 11:49 ` Kalin KOZHUHAROV
2006-01-01 13:09 ` Keith Owens
2006-01-01 12:00 ` Adrian Bunk [this message]
2006-01-02 7:19 ` Kalin KOZHUHAROV
2005-12-30 8:25 ` Jesper Juhl
-- strict thread matches above, loose matches on Subject: below --
2006-01-02 5:59 Mukund JB.
2006-01-02 7:21 ` Kalin KOZHUHAROV
2005-12-30 7:25 Mukund JB.
2005-12-31 0:42 ` Jiri Slaby
2005-12-30 5:46 Mukund JB.
2005-12-30 6:58 ` Alessandro Suardi
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=20060101120057.GS3811@stusta.de \
--to=bunk@stusta.de \
--cc=kalin@thinrope.net \
--cc=linux-kernel@vger.kernel.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