On Fri, Jul 01, 2016 at 18:40:00 +0200, Ernst Reissner wrote:
> well, I updated to include your fix.
> Things became better but still not ok.
> New output ends as follows:
>
> YACC libinterp/parse-tree/oct-parse.h
> libinterp/parse-tree/oct-parse.output is unchanged
> libinterp/parse-tree/oct-parse.h is unchanged
> libinterp/parse-tree/oct-parse.cc is unchanged
> YACC libinterp/corefcn/oct-tex-parser.h
> libinterp/corefcn/oct-tex-parser.output is unchanged
> libinterp/corefcn/oct-tex-parser.h is unchanged
> libinterp/corefcn/oct-tex-parser.cc is unchanged
> GEN build-aux/mk-f77-def.sh
> config.status: creating build-aux/mk-f77-def.sh-tmp
> config.status: executing build-aux/mk-f77-def.sh commands
> build-aux/mk-f77-def.sh is unchanged
> GEN build-aux/subst-f77-isnan-macro.sh
> config.status: creating build-aux/subst-f77-isnan-macro.sh-tmp
> config.status: executing build-aux/subst-f77-isnan-macro.sh commands
> build-aux/subst-f77-isnan-macro.sh is unchanged
> GEN build-aux/subst-script-vals.sh
> config.status: creating build-aux/subst-script-vals.sh-tmp
> config.status: executing build-aux/subst-script-vals.sh commands
> build-aux/subst-script-vals.sh is unchanged
> GEN build-aux/mk-default-qt-settings.sh
> config.status: creating build-aux/mk-default-qt-settings.sh-tmp
> config.status: executing build-aux/mk-default-qt-settings.sh commands
> build-aux/mk-default-qt-settings.sh is unchanged
> TEXI2DVI doc/interpreter/octave.dvi
> /usr/bin/texi2dvi: etex exited with bad status, quitting.
> Makefile:27444: recipe for target 'doc/interpreter/octave.dvi' failed
> make[2]: *** [doc/interpreter/octave.dvi] Error 1
> make[2]: Leaving directory '/home/ernst/Octave/octave/.build'
> Makefile:25985: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/home/ernst/Octave/octave/.build'
> Makefile:9822: recipe for target 'all' failed
> make: *** [all] Error 2
> address@hidden:~/Octave/octave/.build>
This looks like bug #48172 [1]. What OS / distribution are you building
on? If it is that bug, we don't currently have a solution or workaround.