Re: automake reports .lo file created with and without libtool

[Skip Montanaro]

(This problem is taking on a life of its own, so I bit the bullet and
subscribed to the list...)

I need to backpedal a little on my earlier statement.  Regarding eliminating
duplicate library targets, I said:

    Commenting out the first two lines does get rid of the error message and
    my build seems to work.

Unfortunately, it didn't quite work.  It appeared to work, but only because
after the deletion and reconfiguring, "make distclean" wasn't as meticulous
about deleting archive libraries without the static library build target
present.  There was still a libalf.a left around to link against.

After commenting out the static lib lines, I executed

    aclocal && automake && autoconf
    ./configure
    make dist-all

on my laptop then copied the .tar.gz file to another remote machine.  After
unpacking it into a new directory I executed:

    ./configure
    make check

and got this error:

    gcc -DHAVE_CONFIG_H -I. -I. -I..     -g -O2 -c `test -f alftest.c || echo 
'./'`alftest.c
    make[2]: *** No rule to make target `../src/libalf.a', needed by `alftest'. 
 Stop.

test/Makefile.am is

    check_PROGRAMS = alftest

    alftest_SOURCES = alftest.c

    alftest_LDADD = ../src/libalf.a

I want the test program linked with the static library in the build tree to
avoid inadvertently linking with any previously installed shared libraries,
so I explicitly mentioned the .a file.

The .a file isn't getting built if I run "make" or "make check".  The reason
I didn't notice it before was that "make distclean" doesn't delete the
static library without the build lines in Makefile.am.

For now it looks like I will have to add the static library build lines back
to src/Makefile.am and put up with the warning message from automake.  Any
suggestions about alternative approaches would be gladly received.

-- 
Skip Montanaro (address@hidden - http://www.mojam.com/)