From: Marc Giger <gigerstyle@gmx.ch>
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 12:13:03 +0100 [thread overview]
Message-ID: <20060101121303.488e634b@vaio.gigerstyle.ch> (raw)
In-Reply-To: <dp89d4$u0i$1@sea.gmane.org>
On Sun, 01 Jan 2006 19:03:15 +0900
Kalin KOZHUHAROV <kalin@thinrope.net> wrote:
> Chris White wrote:
> > On Friday 30 December 2005 16:04, Mukund JB. wrote:
> >
> >>Dear Alessandro,
> >>
> >>Thanks for the reply.
> >>What does that the make CC=<path_to_your_gcc_3.3> do?
> >>Will it set my gcc default build configuration to gcc 3.3?
> >
> >
> > Not Alessandro but,
> >
> > CC sets the CC makefile variable. When the kernel build system goes
> > to compile something, it doesn't call on gcc directly, but rather
> > what the variable CC is set to. By setting it to your gcc 3.3
> > compiler, it will use that instead.
> >
> >
> >>I mean the general procedure is make bzImage; make modules....
> >>How do I do these:
> >>
> >>Will I have to do it like:
> >> make bzImage cc=<gcc path>
> >
> >
> > make CC=<gcc path> bzImage
> >
> > note the case sensitivity, which tends to be somewhat of a pain for
> > new *nix users.
>
> 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.
Why would you "hardwire" it?
#export CC="distcc"
should do it.
It seems you forgot to specify the compiler:
#export CC="distcc <arch-blablabla->gcc" should be the correct way. What
I do is:
#export DISTCC_HOSTS="localhost <machine1 machine2 machineN>"
#make CC="distcc ccache gcc" -j5 bzImage modules
Marc
next prev parent reply other threads:[~2006-01-01 11:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 7:04 Mukund JB.
2005-12-30 7:24 ` Chris White
2006-01-01 10:03 ` Kalin KOZHUHAROV
2006-01-01 11:13 ` Marc Giger [this message]
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
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=20060101121303.488e634b@vaio.gigerstyle.ch \
--to=gigerstyle@gmx.ch \
--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
Powered by JetHome