mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] 2.5.40 kbuild bug: mrproper removes files it shouldn't remove
Date: Mon, 7 Oct 2002 18:08:24 +0200 (MET DST)	[thread overview]
Message-ID: <200210071608.SAA03742@harpo.it.uu.se> (raw)

'make mrproper' incorrectly deletes *~-style editor backup files
from the top-level directory. This bug was introduced in 2.5.29
when the top-level Makefile was changed to remain in the top-level
directory when invoking DocBook's Makefile:

(snippet from patch-2.5.29):
>--- a/Makefile	Fri Jul 26 19:58:50 2002
>+++ b/Makefile	Fri Jul 26 19:58:50 2002
>@@ -650,7 +650,7 @@
> 		-name .\*.tmp -o -name .\*.d \) -type f -print \
> 		| grep -v lxdialog/ | xargs rm -f
> 	@rm -f $(CLEAN_FILES)
>-	@$(MAKE) -C Documentation/DocBook clean
>+	@$(MAKE) -f Documentation/DocBook/Makefile clean
> 
> mrproper: clean archmrproper
> 	@echo 'Making mrproper'

The problem is that DocBook's 'make clean' rule contains

clean:
	@echo 'Cleaning up (DocBook)'
	@rm -f core *~

so the rm now removes files from the wrong directory. Not good.

Since the top-level Makefile removes all core files, I suggest
simply removing the problematic rm line. Patch below.

/Mikael

--- linux-2.5.40/Documentation/DocBook/Makefile.~1~	Sat Aug  3 00:40:00 2002
+++ linux-2.5.40/Documentation/DocBook/Makefile	Mon Oct  7 17:05:16 2002
@@ -155,7 +155,6 @@
 
 clean:
 	@echo 'Cleaning up (DocBook)'
-	@rm -f core *~
 	@rm -f $(BOOKS)
 	@rm -f $(DVI) $(AUX) $(TEX) $(LOG) $(OUT)
 	@rm -f $(PNG-parportbook) $(EPS-parportbook)

             reply	other threads:[~2002-10-07 16:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07 16:08 Mikael Pettersson [this message]
2002-10-07 16:35 ` John Levon

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=200210071608.SAA03742@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=linux-kernel@vger.kernel.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®