This seems like a good forum, maybe I can get some help here...?

I get this error when I call make install, everything had gone fine until then.
Here is the output I get:

[root@localhost lufs-0.9.7]# make install
Making install in kernel
make[1]: Entering directory `/home/jim/rpms/lufs-0.9.7/kernel'
Making install in Linux
make[2]: Entering directory `/home/jim/rpms/lufs-0.9.7/kernel/Linux'
Making install in 2.4
make[3]: Entering directory `/home/jim/rpms/lufs-0.9.7/kernel/Linux/2.4'
make[4]: Entering directory `/home/jim/rpms/lufs-0.9.7/kernel/Linux/2.4'
make[4]: Nothing to be done for `install-exec-am'.
/bin/sh ../../../config/mkinstalldirs /lib/modules/2.4.22-1.2149.nptl/kernel/fs/lufs
mkdir -p -- /lib/modules/2.4.22-1.2149.nptl/kernel/fs/lufs
/bin/sh ../../../libtool --mode=install /usr/bin/install -c lufs.o /lib/modules/2.4.22-1.2149.nptl/kernel/fs/lufs/lufs.o
/usr/bin/install -c lufs.o /lib/modules/2.4.22-1.2149.nptl/kernel/fs/lufs/lufs.o
make install-data-hook
make[5]: Entering directory `/home/jim/rpms/lufs-0.9.7/kernel/Linux/2.4'
depmod -aq
make[5]: depmod: Command not found
make[5]: *** [install-data-hook] Error 127
make[5]: Leaving directory `/home/jim/rpms/lufs-0.9.7/kernel/Linux/2.4'
make[4]: *** [install-data-am] Error 2
make[4]: Leaving directory `/home/jim/rpms/lufs-0.9.7/kernel/Linux/2.4'
make[3]: *** [install-am] Error 2
make[3]: Leaving directory `/home/jim/rpms/lufs-0.9.7/kernel/Linux/2.4'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/home/jim/rpms/lufs-0.9.7/kernel/Linux'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/jim/rpms/lufs-0.9.7/kernel'
make: *** [install-recursive] Error 1

now, there IS a file /sbin/depmod, but this is not on the PATH env var. Is this a case fo having to just add /sbin to PATH and compiling again?

If I try to install again, will I have to do the configure and make bits again?

Thanks a lot if anyone can help me. I'm getting there with linux now, soon I'll be able to help out too (at least on the easy ones!)

normally /sbin should be in root's path, so add it and try again

The output of "configure" is saved so you should just be able to "make" and then "make install" (unless you want to change the configuration options).

Good Luck
Alan

Hmmm... here's a confusing little thing...

In my /etc/profile I have:

pathmunge () {
if ! echo $PATH | /bin/egrep -q "(^|:)$1($|:)" ; then
if [ "$2" = "after" ] ; then
PATH=$PATH:$1
else
PATH=$1:$PATH
fi
fi
}

# Path manipulation
if [ `id -u` = 0 ]; then
pathmunge /sbin
pathmunge /usr/sbin
pathmunge /usr/local/sbin
fi

isn't this munging /sbin to the path for the root user?
if I su and printenv PATH I get none of these on it

I'm a bit stuck here now. What are the pros / cons of just adding the sbin paths in ~root/.bashrc?
I can see why the if in my profiles should work, anyone got any idea why it isn't doing? If I can find out what's wrong with this script I can submit a fix to the fedora project.