For some reason, these targets are missing although others from the
same family are present. This looks like an oversight.
This enables calling 'make install-dvi' from the top-level build
directory.
install-exec:
install-info:
install-html:
+install-dvi:
install-pdf:
+install-ps:
install-data: install-data-@USE_NLS@
install-data-no: all
install-data-yes: all
install-exec:
install-info:
install-html:
+install-dvi:
install-pdf:
+install-ps:
install-data: install-data-@USE_NLS@
install-data-no: all
install-data-yes: all
install-exec:
install-info:
install-html:
+install-dvi:
install-pdf:
+install-ps:
install-data: install-data-@USE_NLS@
install-data-no: all
install-data-yes: all
install-exec:
install-info:
install-html:
+install-dvi:
install-pdf:
+install-ps:
install-data: install-data-@USE_NLS@
install-data-no: all
install-data-yes: all
install-exec:
install-info:
install-html:
+install-dvi:
install-pdf:
+install-ps:
install-data: install-data-@USE_NLS@
install-data-no: all
install-data-yes: all
install-exec:
install-info:
install-html:
+install-dvi:
install-pdf:
+install-ps:
install-data: install-data-@USE_NLS@
install-data-no: all
install-data-yes: all
install-exec:
install-info:
install-html:
+install-dvi:
install-pdf:
+install-ps:
install-data: install-data-@USE_NLS@
install-data-no: all
install-data-yes: all