From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: [build bug] x86_64, -git: Error: unknown pseudo-op: `.cfi_signal_frame'
Date: Tue, 17 Oct 2006 09:37:22 +0000 (UTC) [thread overview]
Message-ID: <slrnej8lv9.2lu.olecom@flower.upol.cz> (raw)
In-Reply-To: 20061016064300.GA5839@elte.hu
Hallo.
On 2006-10-16, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
>> 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?
Do you mean 'CROSS_COMPILE' ?
> this did not solve it either - it seems if both CROSS and CC are set
> then CC overrides it and CROSS is ignored? Removing the CC override
> solved the problem. But how do i insert the 'distcc' that way? Seems
> like a Kbuild breakage to me.
CC with friends is set like this:
+--[linux/Makefile]
|[...]
|AS = $(CROSS_COMPILE)as
|LD = $(CROSS_COMPILE)ld
|CC = $(CROSS_COMPILE)gcc
|CPP = $(CC) -E
|[...]
+--
So, i think, you must set 'CROSS_COMPILE' first and then 'CC' like this:
(exporing PATH in shell, of course)
+--
$ make CROSS_COMPILE=x86_64-pc-linux- 'CC=distcc $(CROSS_COMPILE)gcc'
+--
(BTW, it's funny to see arch-*unknown*-linux...
Like something is deeply hidden and is a very big secret ;)
____
prev parent reply other threads:[~2006-10-17 9:37 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
2006-10-16 6:43 ` Ingo Molnar
2006-10-16 20:06 ` Sam Ravnborg
2006-10-17 9:37 ` Oleg Verych [this message]
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=slrnej8lv9.2lu.olecom@flower.upol.cz \
--to=olecom@flower.upol.cz \
--cc=linux-kernel@vger.kernel.org \
/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.