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]

Date:	Mon, 16 Oct 2006 08:36:02 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Nicholas Miell <nmiell@...cast.net>
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'


* Nicholas Miell <nmiell@...cast.net> wrote:

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

the broken one is:

 GNU assembler 2.14.90.0.8 20040114

the working one is:

 GNU assembler 2.16.91.0.6 20060212

i guess i found the reason for the breakage: i was using a 
cross-compiling setup via the following script:

 make -j165 bzImage ARCH=x86_64 CC='distcc /opt/crosstool/gcc-4.0.2-glibc-2.3.6/x86_64-unknown-linux-gnu/bin/x86_64-unknown-linux-gnu-gcc'

Note that i override 'CC' instead of specifying a 'CROSS' prefix. I 
suspect this means as-instr does not switch over to the 
cross-environment and thus mis-detected the gas version?

	Ingo
-
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/