[PVFS2-developers] [PATCH] Makefile.in:Use prefix in kmod_install
robl at mcs.anl.gov
Tue Jun 7 14:40:49 EDT 2005
On Sun, Apr 17, 2005 at 04:31:42PM +0200, Lars Roland wrote:
> Trivial patch for makefile.in (works against current CVS and 1.0.1)
> that makes kmod_install and kmod24_install use prefix.
I've taken a slightly different approach. I know using $prefix makes
things easy if you are making an .rpm or .deb, but if you are building
from a tarball, the kernel module will end up in a nonstandard place.
What i've done instead is let people provide a 'kmod_path' when they
run 'make kmod_install', which will put the kernel module somewhere
% make kmod_prefix=/tmp/blah kmod_install
install -m 755 src/apps/kernel/linux/pvfs2-client-core src/apps/kernel/linux/pvfs2-client /home/robl/work/soft/pvfs2/sbin
install -d /tmp/blah/lib/modules/22.214.171.124/kernel/fs
install -m 755 src/kernel/linux-2.6/pvfs2.ko /tmp/blah/lib/modules/126.96.36.199/kernel/fs
i.e. binaries (pvfs2-client and pvfs2-client-core) use $prefix, and
kernel modules use $kmod_prefix.
I'm taking the easy way out and not making this a configure-time
settting. I'm assuming the only people who might want to install a
kernel module in a nonstandard place are packagers, whom I trust can
add 'kmod_path=/some/preferred/path' to their packaging scripts.
Comments? It's been a long time since i had to worry about making
rpms so I might be overlooking something important for packagers.
Mathematics and Computer Science Division A215 0178 EA2D B059 8CDF
Argonne National Labs, IL USA B29D F333 664A 4280 315B
More information about the PVFS2-developers