From: akpm@linux-foundation.org
To: mmarek@suse.cz
Cc: linux-kbuild@vger.kernel.org, akpm@linux-foundation.org,
tiago.maluta@gmail.com
Subject: [patch 1/1] kbuild: fix CONFIG_CROSS_COMPILE issue in .config
Date: Tue, 20 Jul 2010 15:23:27 -0700 [thread overview]
Message-ID: <201007202223.o6KMNRpV021360@imap1.linux-foundation.org> (raw)
From: Tiago Maluta <tiago.maluta@gmail.com>
Linux has an recent option to define CROSS_COMPILE in menuconfig.
Typically, one of the options when building for another target is
('arm' is just an example):
# make ARCH=arm CROSS_COMPILE=arm-cc O=../build
If I omit CROSS_COMPILE and use the new way in .config:
CONFIG_CROSS_COMPILE="arm-cc"
I got:
cc1: error: unrecognized command line option "-mlittle-endian"
cc1: error: unrecognized command line option "-mabi=aapcs-linux"
cc1: error: unrecognized command line option "-mno-thumb-interwork"
/usr/src/linux/kernel/bounds.c:1: error: bad value (armv5t) for -march= switch
/usr/src/linux/kernel/bounds.c:1: error: bad value (armv5t) for -mtune= switch
make[2]: *** [kernel/bounds.s] Error 1
make[1]: *** [prepare0] Error 2
make: *** [sub-make] Error 2
Verbose output clearly says that I'm using the host compiler instead cross
compiler. This patch fixed my problem.
Cc: Michal Marek <mmarek@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN Makefile~kbuild-fix-config_cross_compile-issue-in-config Makefile
--- a/Makefile~kbuild-fix-config_cross_compile-issue-in-config
+++ a/Makefile
@@ -190,7 +190,7 @@ SUBARCH := $(shell uname -m | sed -e s/i
export KBUILD_BUILDHOST := $(SUBARCH)
ARCH ?= $(SUBARCH)
CROSS_COMPILE ?=
-CROSS_COMPILE ?= $(CONFIG_CROSS_COMPILE:"%"=%)
+CROSS_COMPILE := $(shell grep CONFIG_CROSS_COMPILE .config | cut -d'"' -f2)
# Architecture as present in compile.h
UTS_MACHINE := $(ARCH)
_
reply other threads:[~2010-07-20 22:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201007202223.o6KMNRpV021360@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=tiago.maluta@gmail.com \
/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.