public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Roland McGrath <roland@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-kbuild@vger.kernel.org
Subject: Re: 2.6.25-rc2 vdso_install breaks user "make install"
Date: Sat, 16 Feb 2008 04:53:25 +0100	[thread overview]
Message-ID: <47B65E35.8020905@keyaccess.nl> (raw)
In-Reply-To: <20080216034211.8DD03270193@magilla.localdomain>

On 16-02-08 04:42, Roland McGrath wrote:

> Perhaps it makes more sense to have vdso_install be a dependency of 
> modules_install rather than install, since they both put things in
> /lib/modules.

Would work for me -- modules_install ofcourse runs as root.

> The installed vdso images are potentially useful for a kernel when you 
> aren't bothering to build or install any modules, but those images are
> only ever useful for sophisticated debugging uses anyway.
> 
> Sam, any thoughts?  (See arch/x86/Makefile and arch/powerpc/Makefile.)

Or maybe update the installkernel "protocol" to add these in?

> The only kind of install runs I actually care about are for packaging 
> system builds.  There the packaged build does 'make vdso_install' 
> explicitly anyway (at least Fedora rpms' .spec does).  So if the
> consensus is just to drop the dependency on vdso_install completely, I
> don't object.

Did that for now...

Rene.

  reply	other threads:[~2008-02-16  3:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16  3:31 2.6.25-rc2 vdso_install breaks user "make install" Rene Herman
2008-02-16  3:42 ` Roland McGrath
2008-02-16  3:53   ` Rene Herman [this message]
2008-02-16 11:36   ` Sam Ravnborg
2008-02-17 19:35     ` Sam Ravnborg
2008-02-17 19:53       ` Ingo Molnar

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=47B65E35.8020905@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox