#12 Make Install failure on Fedora 3

open
nobody
5
5 days ago
2005-06-10
Ashley
No

I am trying to get lufs working on fedora core 3,
kernel 2.6.11-1.27_FC3

I get the follwoing output from make install

[root@flyhalf lufs-0.9.7]# make install
Making install in kernel
make[1]: Entering directory `/downloads/lufs-0.9.7/kernel'
Making install in Linux
make[2]: Entering directory
`/downloads/lufs-0.9.7/kernel/Linux'
Making install in 2.6
make[3]: Entering directory
`/downloads/lufs-0.9.7/kernel/Linux/2.6'
make -C /lib/modules/`uname -r`/build SUBDIRS=`pwd` modules
make[4]: Entering directory
`/lib/modules/2.6.11-1.27_FC3/build'
Building modules, stage 2.
MODPOST
*** Warning: "kill_proc_info"
[/downloads/lufs-0.9.7/kernel/Linux/2.6/lufs.ko] u
ndefined!
make[4]: Leaving directory
`/lib/modules/2.6.11-1.27_FC3/build'
make[3]: Leaving directory
`/downloads/lufs-0.9.7/kernel/Linux/2.6'
make[3]: Entering directory
`/downloads/lufs-0.9.7/kernel/Linux'
make[4]: Entering directory
`/downloads/lufs-0.9.7/kernel/Linux'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory
`/downloads/lufs-0.9.7/kernel/Linux'
make[3]: Leaving directory
`/downloads/lufs-0.9.7/kernel/Linux'
make[2]: Leaving directory
`/downloads/lufs-0.9.7/kernel/Linux'
make[2]: Entering directory `/downloads/lufs-0.9.7/kernel'
make[3]: Entering directory `/downloads/lufs-0.9.7/kernel'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/downloads/lufs-0.9.7/kernel'
make[2]: Leaving directory `/downloads/lufs-0.9.7/kernel'
make[1]: Leaving directory `/downloads/lufs-0.9.7/kernel'
Making install in lufsd
make[1]: Entering directory `/downloads/lufs-0.9.7/lufsd'
make[2]: Entering directory `/downloads/lufs-0.9.7/lufsd'
/bin/sh ../config/mkinstalldirs /usr/local/bin
/bin/sh ../libtool --mode=install /usr/bin/install -c
lufsd /usr/local/bin/luf sd
/usr/bin/install -c lufsd /usr/local/bin/lufsd
/bin/sh ../config/mkinstalldirs /usr/local/bin
/usr/bin/install -c lussh /usr/local/bin/lussh
make install-exec-hook
make[3]: Entering directory `/downloads/lufs-0.9.7/lufsd'
lufsd post install configuration...
/bin/sh ../config/mkinstalldirs /sbin
ln -fs /usr/local/bin/lufsd /sbin/mount.lufs
make[3]: Leaving directory `/downloads/lufs-0.9.7/lufsd'
/bin/sh ../config/mkinstalldirs /etc
/usr/bin/install -c -m 644 lufsd.conf /etc/lufsd.conf
make[2]: Leaving directory `/downloads/lufs-0.9.7/lufsd'
make[1]: Leaving directory `/downloads/lufs-0.9.7/lufsd'
Making install in filesystems
make[1]: Entering directory
`/downloads/lufs-0.9.7/filesystems'
Making install in localfs
make[2]: Entering directory
`/downloads/lufs-0.9.7/filesystems/localfs'
make[3]: Entering directory
`/downloads/lufs-0.9.7/filesystems/localfs'
/bin/sh ../../config/mkinstalldirs /usr/local/lib
/bin/sh ../../libtool --mode=install /usr/bin/install
-c liblufs-localfs.la /u sr/local/lib/liblufs-localfs.la
/usr/bin/install -c .libs/liblufs-localfs.so.2.0.0
/usr/local/lib/liblufs-localf s.so.2.0.0
(cd /usr/local/lib && rm -f liblufs-localfs.so.2 && ln
-s liblufs-localfs.so.2.0 .0 liblufs-localfs.so.2)
(cd /usr/local/lib && rm -f liblufs-localfs.so && ln -s
liblufs-localfs.so.2.0.0 liblufs-localfs.so)
/usr/bin/install -c .libs/liblufs-localfs.lai
/usr/local/lib/liblufs-localfs.la
PATH="$PATH:/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[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory
`/downloads/lufs-0.9.7/filesystems/localfs'
make[2]: Leaving directory
`/downloads/lufs-0.9.7/filesystems/localfs'
Making install in locasefs
make[2]: Entering directory
`/downloads/lufs-0.9.7/filesystems/locasefs'
make[3]: Entering directory
`/downloads/lufs-0.9.7/filesystems/locasefs'
/bin/sh ../../config/mkinstalldirs /usr/local/lib
/bin/sh ../../libtool --mode=install /usr/bin/install
-c liblufs-locasefs.la / usr/local/lib/liblufs-locasefs.la
/usr/bin/install -c .libs/liblufs-locasefs.so.2.0.0
/usr/local/lib/liblufs-locas efs.so.2.0.0
(cd /usr/local/lib && rm -f liblufs-locasefs.so.2 && ln
-s liblufs-locasefs.so.2 .0.0 liblufs-locasefs.so.2)
(cd /usr/local/lib && rm -f liblufs-locasefs.so && ln
-s liblufs-locasefs.so.2.0 .0 liblufs-locasefs.so)
/usr/bin/install -c .libs/liblufs-locasefs.lai
/usr/local/lib/liblufs-locasefs.l a
PATH="$PATH:/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[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory
`/downloads/lufs-0.9.7/filesystems/locasefs'
make[2]: Leaving directory
`/downloads/lufs-0.9.7/filesystems/locasefs'
Making install in ftpfs
make[2]: Entering directory
`/downloads/lufs-0.9.7/filesystems/ftpfs'
make[3]: Entering directory
`/downloads/lufs-0.9.7/filesystems/ftpfs'
/bin/sh ../../config/mkinstalldirs /usr/local/lib
/bin/sh ../../libtool --mode=install /usr/bin/install
-c liblufs-ftpfs.la /usr /local/lib/liblufs-ftpfs.la
/usr/bin/install -c .libs/liblufs-ftpfs.so.2.0.0
/usr/local/lib/liblufs-ftpfs.so .2.0.0
(cd /usr/local/lib && rm -f liblufs-ftpfs.so.2 && ln -s
liblufs-ftpfs.so.2.0.0 l iblufs-ftpfs.so.2)
(cd /usr/local/lib && rm -f liblufs-ftpfs.so && ln -s
liblufs-ftpfs.so.2.0.0 lib lufs-ftpfs.so)
/usr/bin/install -c .libs/liblufs-ftpfs.lai
/usr/local/lib/liblufs-ftpfs.la
PATH="$PATH:/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[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory
`/downloads/lufs-0.9.7/filesystems/ftpfs'
make[2]: Leaving directory
`/downloads/lufs-0.9.7/filesystems/ftpfs'
Making install in gnetfs
make[2]: Entering directory
`/downloads/lufs-0.9.7/filesystems/gnetfs'
make[3]: Entering directory
`/downloads/lufs-0.9.7/filesystems/gnetfs'
/bin/sh ../../config/mkinstalldirs /usr/local/lib
/bin/sh ../../libtool --mode=install /usr/bin/install
-c liblufs-gnetfs.la /us r/local/lib/liblufs-gnetfs.la
/usr/bin/install -c .libs/liblufs-gnetfs.so.1.0.0
/usr/local/lib/liblufs-gnetfs. so.1.0.0
(cd /usr/local/lib && rm -f liblufs-gnetfs.so.1 && ln
-s liblufs-gnetfs.so.1.0.0 liblufs-gnetfs.so.1)
(cd /usr/local/lib && rm -f liblufs-gnetfs.so && ln -s
liblufs-gnetfs.so.1.0.0 l iblufs-gnetfs.so)
/usr/bin/install -c .libs/liblufs-gnetfs.lai
/usr/local/lib/liblufs-gnetfs.la
PATH="$PATH:/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[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory
`/downloads/lufs-0.9.7/filesystems/gnetfs'
make[2]: Leaving directory
`/downloads/lufs-0.9.7/filesystems/gnetfs'
Making install in sshfs
make[2]: Entering directory
`/downloads/lufs-0.9.7/filesystems/sshfs'
make[3]: Entering directory
`/downloads/lufs-0.9.7/filesystems/sshfs'
/bin/sh ../../config/mkinstalldirs /usr/local/lib
/bin/sh ../../libtool --mode=install /usr/bin/install
-c liblufs-sshfs.la /usr /local/lib/liblufs-sshfs.la
/usr/bin/install -c .libs/liblufs-sshfs.so.2.0.0
/usr/local/lib/liblufs-sshfs.so .2.0.0
(cd /usr/local/lib && rm -f liblufs-sshfs.so.2 && ln -s
liblufs-sshfs.so.2.0.0 l iblufs-sshfs.so.2)
(cd /usr/local/lib && rm -f liblufs-sshfs.so && ln -s
liblufs-sshfs.so.2.0.0 lib lufs-sshfs.so)
/usr/bin/install -c .libs/liblufs-sshfs.lai
/usr/local/lib/liblufs-sshfs.la
PATH="$PATH:/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[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory
`/downloads/lufs-0.9.7/filesystems/sshfs'
make[2]: Leaving directory
`/downloads/lufs-0.9.7/filesystems/sshfs'
make[2]: Entering directory
`/downloads/lufs-0.9.7/filesystems'
make[3]: Entering directory
`/downloads/lufs-0.9.7/filesystems'
make install-exec-hook
make[4]: Entering directory
`/downloads/lufs-0.9.7/filesystems'
filesystems post install configuration...
ldconfig
make[4]: ldconfig: Command not found
make[4]: *** [install-exec-hook] Error 127
make[4]: Leaving directory
`/downloads/lufs-0.9.7/filesystems'
make[3]: *** [install-exec-am] Error 2
make[3]: Leaving directory
`/downloads/lufs-0.9.7/filesystems'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory
`/downloads/lufs-0.9.7/filesystems'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
`/downloads/lufs-0.9.7/filesystems'
make: *** [install-recursive] Error 1

Obviously a couple of error here. ldconfig is located
in /sbin/ as expected.

Any help would be appreciated.

Discussion