it seems to be trying to build the kernel module even though it knows the kernel module is there already.
what you can do is edit configure, look for "subdirs kernel" and comment out those 3 lines
that should get you around this problem.
I follow your way . when I am running
#make install
[root@localhost fuse-2.7.2glfs9]# make install
Making install in include
make[1]: Entering directory `/root/fuse-2.7.2glfs9/include'
make[2]: Entering directory `/root/fuse-2.7.2glfs9/include'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/local/include/fuse" || mkdir -p -- "/usr/local/include/fuse"
/usr/bin/install -c -m 644 'fuse.h' '/usr/local/include/fuse/fuse.h'
/usr/bin/install -c -m 644 'fuse_compat.h' '/usr/local/include/fuse/fuse_compat.h'
/usr/bin/install -c -m 644 'fuse_common.h' '/usr/local/include/fuse/fuse_common.h'
/usr/bin/install -c -m 644 'fuse_common_compat.h' '/usr/local/include/fuse/fuse_common_compat.h'
/usr/bin/install -c -m 644 'fuse_lowlevel.h' '/usr/local/include/fuse/fuse_lowlevel.h'
/usr/bin/install -c -m 644 'fuse_lowlevel_compat.h' '/usr/local/include/fuse/fuse_lowlevel_compat.h'
/usr/bin/install -c -m 644 'fuse_opt.h' '/usr/local/include/fuse/fuse_opt.h'
test -z "/usr/local/include" || mkdir -p -- "/usr/local/include"
/usr/bin/install -c -m 644 'old/fuse.h' '/usr/local/include/fuse.h'
/usr/bin/install -c -m 644 'ulockmgr.h' '/usr/local/include/ulockmgr.h'
make[2]: Leaving directory `/root/fuse-2.7.2glfs9/include'
make[1]: Leaving directory `/root/fuse-2.7.2glfs9/include'
Making install in lib
make[1]: Entering directory `/root/fuse-2.7.2glfs9/lib'
make[2]: Entering directory `/root/fuse-2.7.2glfs9/lib'
test -z "/usr/local/lib" || mkdir -p -- "/usr/local/lib"
/bin/sh ../libtool --mode=install /usr/bin/install -c 'libfuse.la' '/usr/local/lib/libfuse.la'
libtool: install: /usr/bin/install -c .libs/libfuse.so.2.7.2 /usr/local/lib/libfuse.so.2.7.2
libtool: install: (cd /usr/local/lib && { ln -s -f libfuse.so.2.7.2 libfuse.so.2 || { rm -f libfuse.so.2 && ln -s libfuse.so.2.7.2 libfuse.so.2; }; })
libtool: install: (cd /usr/local/lib && { ln -s -f libfuse.so.2.7.2 libfuse.so || { rm -f libfuse.so && ln -s libfuse.so.2.7.2 libfuse.so; }; })
libtool: install: /usr/bin/install -c .libs/libfuse.lai /usr/local/lib/libfuse.la
libtool: install: /usr/bin/install -c .libs/libfuse.a /usr/local/lib/libfuse.a
libtool: install: chmod 644 /usr/local/lib/libfuse.a
libtool: install: ranlib /usr/local/lib/libfuse.a
libtool: finish: PATH="/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/root/bin:/sbin" ldconfig -n /usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,-rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
/bin/sh ../libtool --mode=install /usr/bin/install -c 'libulockmgr.la' '/usr/local/lib/libulockmgr.la'
libtool: install: /usr/bin/install -c .libs/libulockmgr.so.1.0.1 /usr/local/lib/libulockmgr.so.1.0.1
libtool: install: (cd /usr/local/lib && { ln -s -f libulockmgr.so.1.0.1 libulockmgr.so.1 || { rm -f libulockmgr.so.1 && ln -s libulockmgr.so.1.0.1 libulockmgr.so.1; }; })
libtool: install: (cd /usr/local/lib && { ln -s -f libulockmgr.so.1.0.1 libulockmgr.so || { rm -f libulockmgr.so && ln -s libulockmgr.so.1.0.1 libulockmgr.so; }; })
libtool: install: /usr/bin/install -c .libs/libulockmgr.lai /usr/local/lib/libulockmgr.la
libtool: install: /usr/bin/install -c .libs/libulockmgr.a /usr/local/lib/libulockmgr.a
libtool: install: chmod 644 /usr/local/lib/libulockmgr.a
libtool: install: ranlib /usr/local/lib/libulockmgr.a
libtool: finish: PATH="/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/root/bin:/sbin" ldconfig -n /usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,-rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/root/fuse-2.7.2glfs9/lib'
make[1]: Leaving directory `/root/fuse-2.7.2glfs9/lib'
Making install in util
make[1]: Entering directory `/root/fuse-2.7.2glfs9/util'
make[2]: Entering directory `/root/fuse-2.7.2glfs9/util'
test -z "/usr/local/bin" || mkdir -p -- "/usr/local/bin"
/bin/sh ../libtool --mode=install /usr/bin/install -c 'fusermount' '/usr/local/bin/fusermount'
libtool: install: /usr/bin/install -c fusermount /usr/local/bin/fusermount
/bin/sh ../libtool --mode=install /usr/bin/install -c 'ulockmgr_server' '/usr/local/bin/ulockmgr_server'
libtool: install: /usr/bin/install -c ulockmgr_server /usr/local/bin/ulockmgr_server
mkdir -p -- /sbin
/usr/bin/install -c ./mount.fuse /sbin/mount.fuse
mkdir -p -- /etc/init.d
/usr/bin/install -c ./init_script /etc/init.d/fuse
make install-exec-hook
make[3]: Entering directory `/root/fuse-2.7.2glfs9/util'
chown root /usr/local/bin/fusermount
chmod u+s /usr/local/bin/fusermount
make[3]: Leaving directory `/root/fuse-2.7.2glfs9/util'
mkdir -p -- /etc/udev/rules.d
/usr/bin/install -c -m 644 ./udev.rules /etc/udev/rules.d/99-fuse.rules
make[2]: Leaving directory `/root/fuse-2.7.2glfs9/util'
make[1]: Leaving directory `/root/fuse-2.7.2glfs9/util'
Making install in example
make[1]: Entering directory `/root/fuse-2.7.2glfs9/example'
make[2]: Entering directory `/root/fuse-2.7.2glfs9/example'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/root/fuse-2.7.2glfs9/example'
make[1]: Leaving directory `/root/fuse-2.7.2glfs9/example'
make[1]: Entering directory `/root/fuse-2.7.2glfs9'
make[2]: Entering directory `/root/fuse-2.7.2glfs9'
make[2]: Nothing to be done for `install-exec-am'.
test -z "/usr/local/lib/pkgconfig" || mkdir -p -- "/usr/local/lib/pkgconfig"
/usr/bin/install -c -m 644 'fuse.pc' '/usr/local/lib/pkgconfig/fuse.pc'
make[2]: Leaving directory `/root/fuse-2.7.2glfs9'
make[1]: Leaving directory `/root/fuse-2.7.2glfs9'
Nothing to be done for `install-exec-am'.
It shows some thing like this . can you help me?
Thanks
L.Mohan
