linux-kernel - Re: [build bug] x86_64, -git: Error: unknown pseudo-op: `.cfi_signal

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1160980603.2388.9.camel@entropy>
Date:	Sun, 15 Oct 2006 23:36:43 -0700
From:	Nicholas Miell <nmiell@...cast.net>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Jan Beulich <jbeulich@...ell.com>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...l.org>, Andi Kleen <ak@...e.de>
Subject: Re: [build bug] x86_64, -git: Error: unknown pseudo-op:
	`.cfi_signal_frame'

On Mon, 2006-10-16 at 08:10 +0200, Ingo Molnar wrote:
> using latest -git i'm getting this build bug on gcc 3.4:
> 
>  arch/x86_64/kernel/entry.S: Assembler messages:
>  arch/x86_64/kernel/entry.S:157: Error: unknown pseudo-op: `.cfi_signal_frame'
>  arch/x86_64/kernel/entry.S:215: Error: unknown pseudo-op: `.cfi_signal_frame'
>  arch/x86_64/kernel/entry.S:333: Error: unknown pseudo-op: `.cfi_signal_frame'
>  arch/x86_64/kernel/entry.S:548: Error: unknown pseudo-op: `.cfi_signal_frame'
> 
>  gcc version 3.4.0 20040129 (Red Hat Linux 3.4.0-0.3)
> 
> using gcc 4.1 it doesnt happen
> 
>  gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)
> 
> this is caused by the following commit:
> 
>  commit adf1423698f00d00b267f7dca8231340ce7d65ef
>  Author: Jan Beulich <jbeulich@...ell.com>
>  Date:   Tue Sep 26 10:52:41 2006 +0200
> 
> reverting that patch solves the build problem and the resulting kernel 
> builds and boots fine.
> 
> 	Ingo

This is a binutils/gas feature; gcc has nothing to do with it. I take it
the gcc 4.1 system is FC5 with binutils 2.16.91.0.6-5 and the gcc 3.4
system is something older?

The kernel build system is supposed to detect gas support
for .cfi_signal_frame -- and while the i386 test is obviously broken
(the i386 test for the directive doesn't actually use the directive),
the AMD64 test looks like it should work (assuming as-instr works).

-- 
Nicholas Miell <nmiell@...cast.net>

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