+Tue May 6 15:22:41 1997 Ian Lance Taylor <ian@cygnus.com>
+
+ * subdirs.am: Fix check for make -k to use $(MAKEFLAGS) and to not
+ get fooled by command line arguments.
+
Sat May 10 15:48:46 1997 Tom Tromey <tromey@cygnus.com>
* m4/ccstdc.m4: Print "none needed" if compiler accepts ANSI C by
+* in --cygnus, clean-info not generated at top level
+
* update text in missing
avoid passive voice
all-recursive install-data-recursive install-exec-recursive \
installdirs-recursive install-recursive uninstall-recursive @INSTALLINFO@ \
check-recursive installcheck-recursive info-recursive dvi-recursive:
- @for subdir in $(SUBDIRS); do \
+ @set fnord $(MAKEFLAGS); amf=$$2; \
+ for subdir in $(SUBDIRS); do \
target=`echo $@ | sed s/-recursive//`; \
echo "Making $$target in $$subdir"; \
(cd $$subdir && $(MAKE) $$target) \
## This trick allows "-k" to keep its natural meaning when running a
## recursive rule.
- || case "$(MFLAGS)" in *k*) fail=yes;; *) exit 1;; esac; \
+ || case "$$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \
done && test -z "$$fail"
## We run all `clean' targets in reverse order. Why? It's an attempt
## bombs.
mostlyclean-recursive clean-recursive distclean-recursive \
maintainer-clean-recursive:
- @rev=''; for subdir in $(SUBDIRS); do rev="$$rev $$subdir"; done; \
+ @set fnord $(MAKEFLAGS); amf=$$2; \
+ rev=''; for subdir in $(SUBDIRS); do rev="$$rev $$subdir"; done; \
for subdir in $$rev; do \
target=`echo $@ | sed s/-recursive//`; \
echo "Making $$target in $$subdir"; \
(cd $$subdir && $(MAKE) $$target) \
## This trick allows "-k" to keep its natural meaning when running a
## recursive rule.
- || case "$(MFLAGS)" in *k*) fail=yes;; *) exit 1;; esac; \
+ || case "$$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \
done && test -z "$$fail"
all-recursive install-data-recursive install-exec-recursive \
installdirs-recursive install-recursive uninstall-recursive @INSTALLINFO@ \
check-recursive installcheck-recursive info-recursive dvi-recursive:
- @for subdir in $(SUBDIRS); do \
+ @set fnord $(MAKEFLAGS); amf=$$2; \
+ for subdir in $(SUBDIRS); do \
target=`echo $@ | sed s/-recursive//`; \
echo "Making $$target in $$subdir"; \
(cd $$subdir && $(MAKE) $$target) \
## This trick allows "-k" to keep its natural meaning when running a
## recursive rule.
- || case "$(MFLAGS)" in *k*) fail=yes;; *) exit 1;; esac; \
+ || case "$$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \
done && test -z "$$fail"
## We run all `clean' targets in reverse order. Why? It's an attempt
## bombs.
mostlyclean-recursive clean-recursive distclean-recursive \
maintainer-clean-recursive:
- @rev=''; for subdir in $(SUBDIRS); do rev="$$rev $$subdir"; done; \
+ @set fnord $(MAKEFLAGS); amf=$$2; \
+ rev=''; for subdir in $(SUBDIRS); do rev="$$rev $$subdir"; done; \
for subdir in $$rev; do \
target=`echo $@ | sed s/-recursive//`; \
echo "Making $$target in $$subdir"; \
(cd $$subdir && $(MAKE) $$target) \
## This trick allows "-k" to keep its natural meaning when running a
## recursive rule.
- || case "$(MFLAGS)" in *k*) fail=yes;; *) exit 1;; esac; \
+ || case "$$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \
done && test -z "$$fail"