From: Don Mullis <dwm@meer.net>
To: linux-kernel@vger.kernel.org
Cc: sam@ravnborg.org
Subject: Re: 2.6.23-mm1 [PATCH] restore default ARCH
Date: Fri, 12 Oct 2007 00:10:43 -0700 [thread overview]
Message-ID: <87ve9c6c5o.fsf_-_@meer.net> (raw)
In-Reply-To: <9dkWK-5Qx-7@gated-at.bofh.it> (KAMEZAWA Hiroyuki's message of "Fri\, 12 Oct 2007 07\:10\:10 +0200")
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> writes:
> [kamezawa@hannibal ref-2.6.23-mm1]$ make menuconfig
> Makefile:456: /home/kamezawa/ref-2.6.23-mm1/arch//Makefile: No such file or directory
> make: *** No rule to make target `/home/kamezawa/ref-2.6.23-mm1/arch//Makefile'. Stop.
> ==
>
> $(ARCH) cannot be detected automatically...
>
> What information is useful for fixing this ?
This works for i386 on Ubuntu:
Definition of ARCH to the empty string defeated default native ARCH
assignment during initial run of make; eliminate said definition.
Signed-off-by: Don Mullis <dwm@meer.net>
---
Makefile | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
Index: linux-2.6.23-mm/Makefile
===================================================================
--- linux-2.6.23-mm.orig/Makefile 2007-10-11 23:28:43.000000000 -0700
+++ linux-2.6.23-mm/Makefile 2007-10-11 23:30:50.000000000 -0700
@@ -189,9 +189,8 @@
# Default value for CROSS_COMPILE is not to prefix executables
# Note: Some architectures assign CROSS_COMPILE in their arch/*/Makefile
-# The empty ARCH and CROSS_COMPILE statements exist so it is easy to
-# patch in hardcoded values for ARCH and CROSS_COMPILE
-ARCH ?=
+# The empty CROSS_COMPILE statement exists so it is easy to
+# patch in a hardcoded value.
CROSS_COMPILE ?=
# Kbuild save the ARCH and CROSS_COMPILE setting in .kbuild
parent reply other threads:[~2007-10-12 7:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <9dkWK-5Qx-7@gated-at.bofh.it>]
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=87ve9c6c5o.fsf_-_@meer.net \
--to=dwm@meer.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.