public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] kbuild: work around distcc/icecc madness
Date: Fri, 20 Mar 2009 20:16:08 +0100	[thread overview]
Message-ID: <1237576568.4667.34.camel@laptop> (raw)
In-Reply-To: <alpine.LFD.2.00.0903201658140.29264@localhost.localdomain>

On Fri, 2009-03-20 at 17:00 +0100, Thomas Gleixner wrote:
> On Fri, 20 Mar 2009, Peter Zijlstra wrote:
> > Yes, this makes it mostly work again... however,
> > 
> > On -linus I can do:
> >   
> > # cat distmake
> > 
> >   #!/bin/bash
> > 
> >   ARCH=$1; shift
> > 
> >   export LD="nice -n19 ${ARCH}-linux-ld"
> >   export AS="distcc ${ARCH}-linux-as"
> >   export CC="distcc ${ARCH}-linux-gcc"
> > 
> >   make LD="$LD" AS="$AS" CC="$CC" -j $DISTCC_SLOTS "$@"
> > 
> > # distmake x86_64 bzImage
> > 
> > to build the tree, and then use: 
> > 
> > # make install
> > 
> > to install the resulting image. Note how the second make will use the
> > system gcc and not the distcc with cross arch toolchain.
> > 
> > This will still start a full rebuild on -tip. When I change my script to
> > use distmake x86_64 install, things work again after this patch.
> 
> Changing from distcc to gcc will start a full rebuild on linus tree as
> well.

I just tried:

root@twins:/mnt/build/linux-2.6# /mnt/md0/cross/bin/x86_64-linux-gcc --version
x86_64-linux-gcc (GCC) 4.3.1 20080510 (prerelease)
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

root@twins:/mnt/build/linux-2.6# gcc --version
gcc (Ubuntu 4.3.2-1ubuntu12) 4.3.2
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

The build with the distcc x86_64-linux-gcc compiler and the install
using the host compiler works just fine on Linus' tree.




  reply	other threads:[~2009-03-20 19:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 21:02 [PATCH] kbuild: work around distcc/icecc madness Thomas Gleixner
2009-03-20  9:22 ` Ingo Molnar
2009-03-20 10:31   ` Thomas Gleixner
2009-03-20 18:59     ` Ingo Molnar
2009-03-20 19:31       ` Thomas Gleixner
2009-03-20 19:33         ` Ingo Molnar
2009-03-20 20:41           ` Thomas Gleixner
2009-03-21 14:18             ` Ingo Molnar
2009-04-02 21:33               ` Thomas Gleixner
2009-04-08 16:13                 ` Ingo Molnar
2009-04-08 16:59                   ` Ingo Molnar
2009-03-20 12:23 ` Peter Zijlstra
2009-03-20 16:00   ` Thomas Gleixner
2009-03-20 19:16     ` Peter Zijlstra [this message]
2009-03-20 21:57       ` Thomas Gleixner
2009-04-02 23:56         ` Johannes Weiner
2009-04-03  0:39           ` Johannes Weiner

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=1237576568.4667.34.camel@laptop \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    /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