depcomp used but not installed

[Pavel Roskin]

Hello!

The conditions under which Automake installs and uses the "depmod" script
are different. It can actually happen that it's not installed but
configure tries to use it.

For example, GNU Midnight Commander is using Automake only on the top
level and for data directories. Automake doesn't see any C files in the
Makefile.am, so it decides not to install depmod. But since AC_PROG_CC is
used, configure tries to use depcomp.

I've written depcomp2.test that demonstrates the problem.

Actually, I don't know how it should be fixed. Either depcomp should be
installed just in case or AM_DEPENDENCIES should be more quiet if it
cannot find depcomp.

Anyway, this test demonstrates error messages from "configure" - this
certainly shouldn't happen.

-- 
Regards,
Pavel Roskin


__________________________________________________
#! /bin/sh

# Test to make sure that depcomp is not used when it's not installed
# From Pavel Roskin.

. $srcdir/defs || exit 1

cat > configure.in << 'END'
AC_INIT(subdir/foo.c)
AM_INIT_AUTOMAKE(nonesuch, nonesuch)
PACKAGE=nonesuch
VERSION=nonesuch
AC_PROG_CC
AC_OUTPUT(Makefile subdir/Makefile)
END

cat > Makefile.am << 'END'
SUBDIRS = subdir
END

rm -f depcomp
mkdir subdir

cat > subdir/Makefile.in << 'END'
foo:
        $(CC) -o foo foo.c
END

: > subdir/foo.c

# Fail gracefully if no autoconf.
$needs_autoconf

# Likewise for gcc.
(gcc -v) > /dev/null 2>&1 || exit 77

$ACLOCAL || exit 1
$AUTOMAKE --add-missing || exit 1
$AUTOCONF || exit 1
CC='gcc' ./configure 2>error.log
test -z "`cat error.log`"
__________________________________________________