From: Bodo Eggert <7eggert@gmx.de>
To: Jan Engelhardt <jengelh@computergmbh.de>,
sam@ravnborg.org, zippel@linux-m68k.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Unfortunate infinite make recursion
Date: Sat, 22 Sep 2007 23:19:30 +0200 [thread overview]
Message-ID: <E1IZCNu-0000ai-Rt@be1.lrz> (raw)
In-Reply-To: 96blF-29e-27@gated-at.bofh.it
Jan Engelhardt <jengelh@computergmbh.de> wrote:
> You can cause a recursion in kbuild/make with the following:
>
> make O=$PWD kernel/time.o
> make mrproper
>
> Of course no one would use O=$PWD (that's just the testcase),
> but this happened too often:
>
> /ws/linux/linux-2.6.23$ make O=/ws/linux/linux-2.6.23 kernel/time.o
> (Oops - should have been O=/ws/linux/obj-2.6.23!)
>
> The make O=$PWD truncates the Makefile, making it necessary to run `git
> checkout Makefile` - should you have git; or reextract the tarball
> (should you /still/ have it). Well, can we catch this case somehow?
You can test for the existence of MAINTAINERS in the build dir and abort
if it's there.
--
My computer isn't that nervous...it's just a bit ANSI.
Friß, Spammer: Z9asY@K.7eggert.dyndns.org nwJ@ACle6hUq.7eggert.dyndns.org
l@zjuq.-z.7eggert.dyndns.org pjy.jbJ@rpodmsnk.7eggert.dyndns.org
next parent reply other threads:[~2007-09-22 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <96blF-29e-27@gated-at.bofh.it>
2007-09-22 21:19 ` Bodo Eggert [this message]
2007-09-22 11:24 Unfortunate infinite make recursion Jan Engelhardt
2007-09-22 15:42 ` Oleg Verych
2007-09-22 20:40 ` Sam Ravnborg
2007-09-22 22:23 ` Oleg Verych
2007-09-23 6:03 ` Sam Ravnborg
2007-09-23 7:37 ` Oleg Verych
2007-09-22 20:52 ` Sam Ravnborg
2007-09-23 6:17 ` Jan Engelhardt
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=E1IZCNu-0000ai-Rt@be1.lrz \
--to=7eggert@gmx.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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