[<prev] [next>] [day] [month] [year] [list]
Message-ID: <87ve9c6c5o.fsf_-_@meer.net>
Date: Fri, 12 Oct 2007 00:10:43 -0700
From: Don Mullis <dwm@...r.net>
To: linux-kernel@...r.kernel.org
Cc: sam@...nborg.org
Subject: Re: 2.6.23-mm1 [PATCH] restore default ARCH
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> writes:
> [kamezawa@...nibal 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@...r.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
-
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/
Powered by blists - more mailing lists