[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20091006193547.GA31106@lixom.net>
Date: Tue, 6 Oct 2009 14:35:47 -0500
From: Olof Johansson <olof@...om.net>
To: sam@...nborg.org
Cc: linux-kernel@...r.kernel.org
Subject: Can't do mrproper without knowing the previous ARCH
Sam,
The saving away of arch/cross info is neat, but some of the side effects
are a bit confusing.
See below, this is from a current git pull as of today:
$ make ARCH=foo foo_defconfig
Makefile:483: /work/olof/linux-2.6/arch/foo/Makefile: No such file or directory
make: *** No rule to make target `/work/olof/linux-2.6/arch/foo/Makefile'. Stop.
$ export ARCH=powerpc
$ make foo_defconfig
Makefile:210: *** ARCH changed from "foo" to "powerpc". Use "make mrproper" to fix it up. Stop.
$ make mrproper
Makefile:210: *** ARCH changed from "foo" to "powerpc". Use "make mrproper" to fix it up. Stop.
$ make ARCH= mrproper
Makefile:571: /work/olof/linux-2.6/arch//Makefile: No such file or directory
make: *** No rule to make target `/work/olof/linux-2.6/arch//Makefile'. Stop.
$ make mrproper
Makefile:210: *** ARCH changed from "foo" to "powerpc". Use "make mrproper" to fix it up. Stop.
$ export ARCH=
$ make mrproper
Makefile:571: /work/olof/linux-2.6/arch/foo/Makefile: No such file or directory
make: *** No rule to make target `/work/olof/linux-2.6/arch/foo/Makefile'. Stop.
$
It would be nice if I could do a make mrproper without knowing the
previous arch that the tree was configured for.
Also, like above, if I set an invalid ARCH I can't seem to get out of
this loop since I can't run mrproper at all. :-)
-Olof
--
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