From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Gregory Haskins <ghaskins@novell.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org, henrix@sapo.pt
Subject: Re: Trouble with make-install from a NFS mount
Date: Wed, 15 Apr 2009 14:29:13 -0700 [thread overview]
Message-ID: <49E651A9.8030409@zytor.com> (raw)
In-Reply-To: <20090415212009.GA27597@uranus.ravnborg.org>
Sam Ravnborg wrote:
>> The problem seems to be that 30-rcX thinks that there are dependencies
>> to update (such as include/config/kernel.release and version.h.tmp)
>> during a make-install operation. Since I am on a root-squashed NFS
>> mount, these files cannot be updated and thus the install fails.
>> Previous trees prior to linux-current (at least up to 2.6.29) did not
>> try to update these files so the install would succeed.
>
> It is because arch/x86/Makefile has
> a dependency on vmlinux for the install target.
>
> I know hpa has had a fix for it but it is not applied.
> I recall there was a trivial bug in the first version.
>
OK, do we have a consensus that this is desirable? I was somewhat
confused if it was desired or considered user error.
I'll clean up the patch and add it in the former case.
-hpa
next prev parent reply other threads:[~2009-04-15 21:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 21:32 Trouble with make-install from a NFS mount Gregory Haskins
2009-04-14 21:36 ` Randy Dunlap
2009-04-15 18:30 ` Gregory Haskins
2009-04-15 20:21 ` Randy Dunlap
2009-04-15 21:13 ` Gregory Haskins
2009-04-15 21:20 ` Sam Ravnborg
2009-04-15 21:29 ` H. Peter Anvin [this message]
2009-04-15 23:46 ` Sam Ravnborg
2009-04-17 17:51 ` [tip:x86/urgent] x86, kbuild: make "make install" not depend on vmlinux tip-bot for H. Peter Anvin
2009-04-17 20:46 ` tip-bot for H. Peter Anvin
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=49E651A9.8030409@zytor.com \
--to=hpa@zytor.com \
--cc=ghaskins@novell.com \
--cc=henrix@sapo.pt \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--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.