Re: [PATCH] kbuild: work around distcc/icecc madness

[Thomas Gleixner]

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/