From: Pavel Roskin <proski@gnu.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Removing .tmp_versions considered harmful
Date: Mon, 24 Apr 2006 15:55:27 -0400 [thread overview]
Message-ID: <1145908527.2292.39.camel@dv> (raw)
In-Reply-To: <20060421073216.GA17492@mars.ravnborg.org>
Hello, Sam!
How about following patch? Something needs to be done before 2.6.17.
Complaints about .tmp_versions are almost in every list about wireless
drivers I'm subscribed to.
I'm not asking to keep *.mod files, just please keep the .tmp_versions
directory.
-------------------------------
Remove *.mod files but not .tmp_versions for external builds
From: Pavel Roskin <proski@gnu.org>
When "make install" is run as root, .tmp_versions is re-created and
becomes owned by root. Subsequent "make" run by user fails because
.tmp_versions cannot be removed.
Signed-off-by: Pavel Roskin <proski@gnu.org>
---
Makefile | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Makefile b/Makefile
index a940eae..6d7db09 100644
--- a/Makefile
+++ b/Makefile
@@ -1086,7 +1086,7 @@ # We are always building modules
KBUILD_MODULES := 1
PHONY += crmodverdir
crmodverdir:
- $(Q)rm -rf $(MODVERDIR)
+ $(Q)rm -f $(MODVERDIR)/*.mod
$(Q)mkdir -p $(MODVERDIR)
PHONY += $(objtree)/Module.symvers
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-04-24 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 4:22 Removing .tmp_versions considered harmful Pavel Roskin
2006-04-21 7:32 ` Sam Ravnborg
2006-04-21 11:55 ` Pavel Roskin
2006-04-24 19:55 ` Pavel Roskin [this message]
2006-04-24 19:58 ` Arjan van de Ven
2006-04-24 20:19 ` Pavel Roskin
2006-04-30 21:47 ` Sam Ravnborg
2006-05-01 0:59 ` Pavel Roskin
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=1145908527.2292.39.camel@dv \
--to=proski@gnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.