All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Nicholas Miell <nmiell@comcast.net>
Cc: Jan Beulich <jbeulich@novell.com>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Andi Kleen <ak@suse.de>
Subject: Re: [build bug] x86_64, -git: Error: unknown pseudo-op: `.cfi_signal_frame'
Date: Mon, 16 Oct 2006 08:36:02 +0200	[thread overview]
Message-ID: <20061016063602.GA4392@elte.hu> (raw)
In-Reply-To: <1160980603.2388.9.camel@entropy>


* Nicholas Miell <nmiell@comcast.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

  reply	other threads:[~2006-10-16  6:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16  6:10 [build bug] x86_64, -git: Error: unknown pseudo-op: `.cfi_signal_frame' Ingo Molnar
2006-10-16  6:33 ` Andrew Morton
2006-10-16  7:00   ` Jan Beulich
2006-10-16  6:36 ` Nicholas Miell
2006-10-16  6:36   ` Ingo Molnar [this message]
2006-10-16  6:43     ` Ingo Molnar
2006-10-16 20:06       ` Sam Ravnborg
2006-10-17  9:37       ` Oleg Verych

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=20061016063602.GA4392@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nmiell@comcast.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.