linux-kernel - Re: 2.6.25-rc2 vdso_install breaks user "make install"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080216034211.8DD03270193@magilla.localdomain>
Date:	Fri, 15 Feb 2008 19:42:11 -0800 (PST)
From:	Roland McGrath <roland@...hat.com>
To:	Rene Herman <rene.herman@...access.nl>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Sam Ravnborg <sam@...nborg.org>, linux-kbuild@...r.kernel.org
Subject: Re: 2.6.25-rc2 vdso_install breaks user "make install"

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.
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.)

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.

Thanks,
Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/