From: Olof Johansson <olof@lixom.net>
To: sam@ravnborg.org
Cc: linux-kernel@vger.kernel.org
Subject: Can't do mrproper without knowing the previous ARCH
Date: Tue, 6 Oct 2009 14:35:47 -0500 [thread overview]
Message-ID: <20091006193547.GA31106@lixom.net> (raw)
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
reply other threads:[~2009-10-06 19:18 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=20091006193547.GA31106@lixom.net \
--to=olof@lixom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®