Subject: bug#14594: depcomp missing from Makefile.in in AM 1.13.3

From: "Jeff Squyres (jsquyres)" <[email-masked]>
Date: Tue, 11 Jun 2013 23:42:16 +0000

Attached is a trivial reproducer showing that Automake is not including depcomp in the generated Makefile.in, which therefore results in a "make dist" tarball being un-buildable.  I have tested with Automake 1.13.3, which I just downloaded from ftp.gnu.org and built myself (paired with Autoconf 2.69).

Three things seem to be necessary for this to happen:

1. configure.ac identifies itself as a foreign project (i.e., AM_INIT_AUTOMAKE([foreign]))
2. The source files must not be in the root (i.e., src/hello.c, not hello.c)
3. depcomp is not present when you run autoreconf

Specifically: the first time you run autoreconf -ivf (e.g., when you get a fresh/clean checkout of a project), depcomp is generated as expected, but it is *not* included in the Makefile.in.  However, if you run autoreconf -ivf a second time, depcomp is then included in Makefile.in.

Instructions for the reproducer:

1. Untar the tarball; cd into automake-1.13.3-bug
2. Run the "./run" script, which does the following:

    rm -f depcomp missing install-sh
    autoreconf -ivf
    grep depcomp Makefile.in
    # Notice that depcomp is not listed in Makefile.in
    # Now run autoreconf a second time
    autoreconf -ivf
    grep depcomp Makefile.in
    # Notice that depcomp is now listed in Makefile.in

-- 
Jeff Squyres
[email-masked]
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/