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: Sun, 30 Apr 2006 20:59:57 -0400 [thread overview]
Message-ID: <1146445197.7879.9.camel@dv> (raw)
In-Reply-To: <20060430214732.GB18257@mars.ravnborg.org>
Hello, Sam!
On Sun, 2006-04-30 at 23:47 +0200, Sam Ravnborg wrote:
> On Mon, Apr 24, 2006 at 03:55:27PM -0400, Pavel Roskin wrote:
> > 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.
>
> What architecture?
> For i386 and x86_64 make install no longer try to compile the kernel.
That's x86_64. It turns out the dependency of "install" on "all" in the
project Makefile was causing .tmp_versions to be re-created. Removing
the dependency on "all" fixes the problem. This is the original rule:
install: all
$(MAKE) $(KBUILD_FLAGS) modules_install \
INSTALL_MOD_DIR=kernel/drivers/net/wireless
$(DEPMOD) -ae
However, I'd rather keep the dependency of "install" on "all". It's
better to compile a few files as root than to install out-of-date
modules. I'm glad that your patch gives me a choice how to write the
project's Makefile.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2006-05-01 1:00 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
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 [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=1146445197.7879.9.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox