Thu Mar 27 17:28:47 1997 Tom Tromey <tromey@cygnus.com>
+ * texi-vers.am (stamp-@VTI@): Make commands silent.
+
+ * Makefile.am (maintainer-check): "true" is ok now.
+
* m4/init.m4: Added optional 3rd argument, which avoids
AC_DEFINE.
## Syntax check with default Perl (on my machine, Perl 5).
$(PERL) -c -w automake
$(PERL) -c -w aclocal
-## Ensure `true' is never used; I've accidentally used it before.
- @if grep '^[^#].*true' $(srcdir)/[a-z]*.am; then \
- echo "can't use 'true' in GNU Makefile" 1>&2; \
- exit 1; \
- else :; fi
## expect no instances of '${...}'. However, $${...} is ok, since that
## is a shell construct, not a Makefile construct.
@if test `fgrep '$${' $(srcdir)/[a-z]*.am | fgrep -v '$$$$' | wc -l` -ne 0; then \
maintainer-check: automake aclocal
$(PERL) -c -w automake
$(PERL) -c -w aclocal
- @if grep '^[^#].*true' $(srcdir)/[a-z]*.am; then \
- echo "can't use 'true' in GNU Makefile" 1>&2; \
- exit 1; \
- else :; fi
@if test `fgrep '$${' $(srcdir)/[a-z]*.am | fgrep -v '$$$$' | wc -l` -ne 0; then \
echo "found too many uses of '\$${'" 1>&2; \
exit 1; \
## Syntax check with default Perl (on my machine, Perl 5).
$(PERL) -c -w automake
$(PERL) -c -w aclocal
-## Ensure `true' is never used; I've accidentally used it before.
- @if grep '^[^#].*true' $(srcdir)/[a-z]*.am; then \
- echo "can't use 'true' in GNU Makefile" 1>&2; \
- exit 1; \
- else :; fi
## expect no instances of '${...}'. However, $${...} is ok, since that
## is a shell construct, not a Makefile construct.
@if test `fgrep '$${' $(srcdir)/[a-z]*.am | fgrep -v '$$$$' | wc -l` -ne 0; then \
## Depend on configure.in so that version number updates cause a
## rebuild.
stamp-@VTI@: @TEXI@ $(top_srcdir)/configure.in
- echo "@set UPDATED `cd $(srcdir) \
+ @echo "@set UPDATED `cd $(srcdir) \
&& $(SHELL) @MDDIR@/mdate-sh @TEXI@`" > @VTI@.tmp
- echo "@set EDITION $(VERSION)" >> @VTI@.tmp
- echo "@set VERSION $(VERSION)" >> @VTI@.tmp
+ @echo "@set EDITION $(VERSION)" >> @VTI@.tmp
+ @echo "@set VERSION $(VERSION)" >> @VTI@.tmp
## Use cp and rm here because some older "mv"s can't move across
## filesystems. Furthermore, GNU "mv" in the AmigaDOS environment
## can't handle this.
- cmp -s @VTI@.tmp $(srcdir)/stamp-@VTI@ \
- || cp @VTI@.tmp $(srcdir)/stamp-@VTI@
- rm -f @VTI@.tmp
+ @cmp -s @VTI@.tmp $(srcdir)/stamp-@VTI@
+ || (echo "Updating $(srcdir)/stamp-@VTI@"; \
+ cp @VTI@.tmp $(srcdir)/stamp-@VTI@)
+ @rm -f @VTI@.tmp
mostlyclean-@VTI@:
rm -f @VTI@.tmp
## Depend on configure.in so that version number updates cause a
## rebuild.
stamp-@VTI@: @TEXI@ $(top_srcdir)/configure.in
- echo "@set UPDATED `cd $(srcdir) \
+ @echo "@set UPDATED `cd $(srcdir) \
&& $(SHELL) @MDDIR@/mdate-sh @TEXI@`" > @VTI@.tmp
- echo "@set EDITION $(VERSION)" >> @VTI@.tmp
- echo "@set VERSION $(VERSION)" >> @VTI@.tmp
+ @echo "@set EDITION $(VERSION)" >> @VTI@.tmp
+ @echo "@set VERSION $(VERSION)" >> @VTI@.tmp
## Use cp and rm here because some older "mv"s can't move across
## filesystems. Furthermore, GNU "mv" in the AmigaDOS environment
## can't handle this.
- cmp -s @VTI@.tmp $(srcdir)/stamp-@VTI@ \
- || cp @VTI@.tmp $(srcdir)/stamp-@VTI@
- rm -f @VTI@.tmp
+ @cmp -s @VTI@.tmp $(srcdir)/stamp-@VTI@
+ || (echo "Updating $(srcdir)/stamp-@VTI@"; \
+ cp @VTI@.tmp $(srcdir)/stamp-@VTI@)
+ @rm -f @VTI@.tmp
mostlyclean-@VTI@:
rm -f @VTI@.tmp