changeset 4654:b9e4ebcad82f

disable doc extraction for optim package Disable the rules for extracting doc strings because they don't work when cross compiling. Our patches to the source files don't touch the doc strings, so there is no need to update them anyway.
author John W. Eaton <jwe@octave.org>
date Tue, 10 Apr 2018 07:50:10 -0400
parents 00e61c4a5657
children c588eacfecab
files src/of-optim-1-fixes.patch
diffstat 1 files changed, 14 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/src/of-optim-1-fixes.patch	Mon Apr 09 12:12:44 2018 -0400
+++ b/src/of-optim-1-fixes.patch	Tue Apr 10 07:50:10 2018 -0400
@@ -127,3 +127,17 @@
        { \
          err = true; \
        }
+diff -uNr a/src/Makefile.in b/src/Makefile.in
+--- a/src/Makefile.in	2016-09-18 13:31:55.000000000 -0400
++++ b/src/Makefile.in	2018-04-10 07:45:13.400473175 -0400
+@@ -102,8 +102,8 @@
+ # Docstrings defined as C strings are obtained from a compiled C
+ # program. This should be the cleanest way to correctly get all
+ # special characters defined in these strings.
+-%.cc.docstrings: %.bin
+-	(echo "### This file is generated automatically from the"; echo "### corresponding .cc file by a Makefile rule."; echo ""; ./$<) > $@
++#%.cc.docstrings: %.bin
++#	(echo "### This file is generated automatically from the"; echo "### corresponding .cc file by a Makefile rule."; echo ""; ./$<) > $@
+ # Explanation of the command after the checks: Macro names are changed
+ # by `sed' so that a different definition can be given to them on the
+ # `cpp' commandline. After running the `cpp' command, one can be sure