From: Sam Ravnborg <sam@ravnborg.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: More Makefile Misery
Date: Sun, 20 Oct 2002 10:08:51 +0200 [thread overview]
Message-ID: <20021020100851.A2191@mars.ravnborg.org> (raw)
In-Reply-To: <20021020012750.C21819@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Sun, Oct 20, 2002 at 01:27:50AM +0100
On Sun, Oct 20, 2002 at 01:27:50AM +0100, Russell King wrote:
> When running make clean on an ARM tree, I get:
>
> make[1]: *** No rule to make target `arch/arm/mach-/Makefile'. Stop.
>
> Seeing as we have many mach-* directories, and the relevant one is
> selected by the relevant .config file.
>
> I see two options:
>
> - recurse into the correct one somehow, given that the .config file may
> have changed since the kernel tree was built.
> - recurse into all mach-* directories for make clean and not for the
> normal build
The cure is simple.
Make sure that MACHINE is always assined a sensible value.
MACHINE := sa1100 # Default value to avoid invalid pathnames with no .config
The recursion into the subdirectories does only take care of files listed
with EXTRA_TARGETS, host-progs, and clean-files.
Only EXTRA_TARGETS are used in the mach- Makefile, and since this is a
*.o file it will anyway be deleted by the find that searches the full
tree when you do a make clean.
Make clean execute a find -name '*.[oas]' and remove all such files,
and use the recursion only to take care of other generated files
spread out over the kernel src tree.
Sam
prev parent reply other threads:[~2002-10-20 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-20 0:27 Russell King
2002-10-20 8:08 ` Sam Ravnborg [this message]
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=20021020100851.A2191@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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
Powered by JetHome