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

On Fri, 20 Mar 2009, Ingo Molnar wrote:
> > ---
> >  scripts/Kbuild.include |    5 +++--
> >  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> Doesnt fully work:
> 
> arch/x86/kernel/entry_32.S:346: Error: unknown pseudo-op: `.cfi_signal_frame'
> arch/x86/kernel/entry_32.S:394: Error: unknown pseudo-op: `.cfi_signal_frame'
> arch/x86/kernel/entry_32.S:519: Error: unknown pseudo-op: `.cfi_signal_frame'
> arch/x86/kernel/entry_32.S:614: Error: unknown pseudo-op: `.cfi_signal_frame'
> arch/x86/kernel/entry_32.S:685: Error: unknown pseudo-op: `.cfi_signal_frame'
> arch/x86/kernel/entry_32.S:754: Error: unknown pseudo-op: `.cfi_signal_frame'
> 
> config attached. Distcc driven build.

Same config works fine here. Do you have different compilers/binutils
on your distcc cluster ? I tripped over this distcc feature in the
past, that's why I have switched to iceccc.

       tglx

  reply	other threads:[~2009-03-20 10:33 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 [this message]
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
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=alpine.LFD.2.00.0903201127360.29264@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).