lkml.org 
[lkml]   [2009]   [Mar]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] kbuild: work around distcc/icecc madness

* Thomas Gleixner <tglx@linutronix.de> wrote:

> 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.

the distcc binutils is different from the host build environment
binutils and compiler. This always worked fine - can we preserve it?

Ingo


\
 
 \ /
  Last update: 2009-03-20 20:03    [W:0.651 / U:0.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site