Re: Automake 1.8.3 doesn't build?

[Alexandre Duret-Lutz <adl at src dot lip6 dot fr>]

>>> "Bob" == Bob Friesenhahn <bfriesen@simple.dallas.tx.us> writes:

 Bob> I regenerated the Automake 1.8.3 Makefiles using Automake 1.8.2 and
 Bob> then I was able to configure and install Automake 1.8.3 under Solaris
 Bob> 9.  I then regenerated the Automake 1.8.3 Makefiles using the just
 Bob> installed Automake 1.8.3 and was able to successfully configure,
 Bob> build, and install Automake 1.8.3.

 Bob> I suspect that there is something wrong with the Automake 1.8.3
 Bob> tarball.  

I bet the only difference between the official 1.8.3 tarball and
the one you generated is that the former tarball uses CVS
Autoconf.  1.8.2 and your regenerated version likely use Autoconf 2.59.

| Making all in . doc m4 lib tests
| cd: no such file or directory: . doc m4 lib tests

The above output comes from

        list='$(SUBDIRS)'; for subdir in $$list; do \
          echo "Making $$target in $$subdir"; \
          if test "$$subdir" = "."; then \
            dot_seen=yes; \
            local_target="$$target-am"; \
          else \
            local_target="$$target"; \
          fi; \
          (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
          ...
        done

Which have been there for years.

This suggests that shell running this code does not split
$list and $subdir get the full list.  Zsh would do that.

Could you compare the output of 
  grep 'SHELL =' Makefile
on the working and non-working tarballs?

CVS Autoconf has a new SHELL selection code.  That could explain it.

This doesn't explain why it works with FreeBSD make, though.  Unless
FreeBSD make ignores SHELL, but that would be a bug.

 Bob> Maybe there is a directory timestamp problem?

I don't know how that could matter.  We do not use directories
as dependencies.
-- 
Alexandre Duret-Lutz