From: Keith Owens <kaos@ocs.com.au>
To: Marc Giger <gigerstyle@gmx.ch>
Cc: Kalin KOZHUHAROV <kalin@thinrope.net>, linux-kernel@vger.kernel.org
Subject: Re: Howto set kernel makefile to use particular gcc
Date: Sun, 01 Jan 2006 22:18:27 +1100 [thread overview]
Message-ID: <23377.1136114307@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 01 Jan 2006 12:13:03 BST." <20060101121303.488e634b@vaio.gigerstyle.ch>
Marc Giger (on Sun, 1 Jan 2006 12:13:03 +0100) wrote:
>Why would you "hardwire" it?
>#export CC="distcc"
>should do it.
Doubt it. From 'info make', Node: Environment.
Variables in `make' can come from the environment in which `make' is
run. Every environment variable that `make' sees when it starts up
is transformed into a `make' variable with the same name and value.
But an explicit assignment in the makefile, or with a command
argument, overrides the environment. (If the `-e' flag is specified,
then values from the environment override assignments in the
makefile. *Note Summary of Options: Options Summary. But this is
not recommended practice.)
The kernel Makefile explicitly sets CC which overrides the environment
value, but does not override a command line definition of CC. IOW, do
not reply on environment variables always working with make.
next prev parent reply other threads:[~2006-01-01 11:18 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 [this message]
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=23377.1136114307@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=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