public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Howto set kernel makefile to use particular gcc
Date: Sun, 01 Jan 2006 20:49:50 +0900	[thread overview]
Message-ID: <dp8fku$bdr$1@sea.gmane.org> (raw)
In-Reply-To: <20060101123729.09c5d76c@vaio.gigerstyle.ch>

You never know where you'll get most response:-)

Marc Giger wrote:
> Keith, your domain seems not to be resolvable...
Yup... very strange. Not proper delegation to zoneedit.com?

kalin@kpc ~ $ whois ocs.com.au |grep ^Name
Name Server:             ns2.zoneedit.com
Name Server:             ns3.zoneedit.com
Name Server:             ns1.ocs.com.au
Name Server IP:          202.147.117.210

kalin@kpc ~ $ dnsq any ocs.com.au ns2.zoneedit.com
255 ocs.com.au:
167 bytes, 1+4+2+0 records, response, authoritative, noerror
query: 255 ocs.com.au
answer: ocs.com.au 7200 A 0.0.0.0
#                     --> H E R E <--
answer: ocs.com.au 7200 NS ns2.zoneedit.com
answer: ocs.com.au 7200 NS ns3.zoneedit.com
answer: ocs.com.au 7200 SOA ns2.zoneedit.com soacontact.zoneedit.com 1135991510
14400 7200 950400 7200
authority: ocs.com.au 7200 NS ns2.zoneedit.com
authority: ocs.com.au 7200 NS ns3.zoneedit.com

kalin@kpc ~ $ dnsq any ocs.com.au 202.147.117.210
255 ocs.com.au:
221 bytes, 1+5+0+4 records, response, authoritative, noerror
query: 255 ocs.com.au
answer: ocs.com.au 172800 SOA mail.ocs.com.au admin.mail.ocs.com.au 2005123101 1
0800 3600 604800 86400
answer: ocs.com.au 172800 MX 0 mail.ocs.com.au
answer: ocs.com.au 172800 NS ns1.ocs.com.au
answer: ocs.com.au 172800 NS ns2.zoneedit.com
answer: ocs.com.au 172800 NS ns3.zoneedit.com
additional: mail.ocs.com.au 172800 A 202.147.117.210
additional: ns1.ocs.com.au 172800 A 202.147.117.210
additional: ns2.zoneedit.com 158763 A 69.72.158.226
additional: ns3.zoneedit.com 158763 A 66.180.174.61

kalin@kpc ~ $ dnsname 202.147.117.210
mail.ocs.com.au

> On Sun, 01 Jan 2006 22:18:27 +1100
> Keith Owens <kaos@ocs.com.au> wrote:
> 
> 
>>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.
> 
> 
> You are absolutely right. Because I never used it in this way, I wrote
> "should":-) I specify it always on the make command line.
> 
> So if Kalin would like to hardwire it, he has to change the CC variable
> in the Makefile...
My point was that changing it in the Makefile does not work.

kpc ~ # grep CC= /usr/src/linux/Makefile
CC=distcc
# echo $CC

kpc ~ # uname -a
Linux kpc 2.6.14.4-K01_P4_desktop #1 Sun Dec 18 22:46:08 JST 2005 i686 Intel(R) Pentium(R) 4 CPU
2.40GHz GenuineIntel GNU/Linux

What I want is making a bunch of kernels in NFS exported /var/kernels/out/`uname -r` and then be
able to `make modules` on other machines without having to recompile the whole thing. All (or
almost?) boxes use gcc-3.4.4 and distcc to share the load.

Kalin.
-- 
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|


  reply	other threads:[~2006-01-01 11:50 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 [this message]
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='dp8fku$bdr$1@sea.gmane.org' \
    --to=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