[Octave-bug-tracker] [bug #51911] doc build fails with texi2dvi/texi2pdf errors, revisited

[Dan Sebald]

URL:
  <http://savannah.gnu.org/bugs/?51911>

                 Summary: doc build fails with texi2dvi/texi2pdf errors,
revisited
                 Project: GNU Octave
            Submitted by: sebald
            Submitted on: Fri 01 Sep 2017 05:52:14 AM UTC
                Category: Documentation
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

I've run into a build problem:


  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
  GEN      libgui/mk-default-qt-settings.sh
config.status: creating libgui/mk-default-qt-settings.sh-tmp
config.status: executing libgui/mk-default-qt-settings.sh commands
  TEXI2DVI doc/interpreter/octave.dvi
/usr/bin/texi2dvi: etex exited with bad status, quitting.


It seems to manifest similar to

https://savannah.gnu.org/bugs/?48172

and discussion thread

http://octave.1599824.n4.nabble.com/Fwd-Re-make-failed-tt4678092.html#a4678102

I got stuck on the fact I had a Sundials IDAKLU issue:


configure:79337: WARNING: --without-osmesa specified.  Functions or features
that depend on OSMesa will be disabled.
configure:79472: WARNING: Sundials IDA library not configured with IDAKLU,
ode15i and ode15s will not support the sparse Jacobian feature
configure:79497: WARNING: JAVA_HOME environment variable not initialized. 
Auto-detection will proceed but is unreliable.
configure:79502: WARNING: No Java executable found.  Octave will not be able
to call Java methods.


, but after trying a half dozen variations on including and excluding OSMesa,
Sundials and Java, I came to the conclusion that none of that seems to
matter.

I can tell what is wrong.  The octave.dvi file is NOT being generated because
it is conditionally commented out of the Makefile:


distclean-libtool:
        -rm -f libtool config.lt
doc/interpreter/$(am__dirstamp):
        @$(MKDIR_P) doc/interpreter
        @: > doc/interpreter/$(am__dirstamp)

#$(srcdir)/doc/interpreter/octave.info: doc/interpreter/octave.texi
$(srcdir)/doc/interpreter/version-octave.texi
#       $(AM_V_MAKEINFO)restore=: && backupdir="$(am__leading_dot)am$$$$" && \
#       am__cwd=`pwd` && $(am__cd) $(srcdir) && \
#       rm -rf $$backupdir && mkdir $$backupdir && \
#       if ($(MAKEINFO) --version) >/dev/null 2>&1; then \
#         for f in $@ address@hidden address@hidden $(@:.info=).i[0-9]
$(@:.info=).i[0-9][0-9]; do \
#           if test -f $$f; then mv $$f $$backupdir; restore=mv; else :; fi; \
#         done; \
#       else :; fi && \
#       cd "$$am__cwd"; \
#       if $(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I doc/interpreter 
-I
$(srcdir)/doc/interpreter \
#        -o $@ $(srcdir)/doc/interpreter/octave.texi; \
#       then \
#         rc=0; \
#         $(am__cd) $(srcdir); \
#       else \
#         rc=$$?; \
#         $(am__cd) $(srcdir) && \
#         $$restore $$backupdir/* `echo "./$@" | sed 's|[^/]*$$||'`; \
#       fi; \
#       rm -rf $$backupdir; exit $$rc

#doc/interpreter/octave.dvi: doc/interpreter/octave.texi
$(srcdir)/doc/interpreter/version-octave.texi doc/interpreter/$(am__dirstamp)
#       
$(AM_V_TEXI2DVI)TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS"
\
#       MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I
doc/interpreter -I $(srcdir)/doc/interpreter' \
#       $(TEXI2DVI) $(AM_V_texinfo) --build-dir=$(@:.dvi=.t2d) -o $@
$(AM_V_texidevnull) \
#       `test -f 'doc/interpreter/octave.texi' || echo
'$(srcdir)/'`doc/interpreter/octave.texi

#doc/interpreter/octave.pdf: doc/interpreter/octave.texi
$(srcdir)/doc/interpreter/version-octave.texi doc/interpreter/$(am__dirstamp)
#       
$(AM_V_TEXI2PDF)TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS"
\
#       MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I
doc/interpreter -I $(srcdir)/doc/interpreter' \
#       $(TEXI2PDF) $(AM_V_texinfo) --build-dir=$(@:.pdf=.t2p) -o $@
$(AM_V_texidevnull) \
#       `test -f 'doc/interpreter/octave.texi' || echo
'$(srcdir)/'`doc/interpreter/octave.texi

#doc/interpreter/octave.html: doc/interpreter/octave.texi
$(srcdir)/doc/interpreter/version-octave.texi doc/interpreter/$(am__dirstamp)
#       $(AM_V_MAKEINFO)rm -rf $(@:.html=.htp)
#       $(AM_V_at)if $(MAKEINFOHTML) $(AM_MAKEINFOHTMLFLAGS) $(MAKEINFOFLAGS) -I
doc/interpreter -I $(srcdir)/doc/interpreter \
#        -o $(@:.html=.htp) `test -f 'doc/interpreter/octave.texi' || echo
'$(srcdir)/'`doc/interpreter/octave.texi; \
#       then \
#         rm -rf $@ && mv $(@:.html=.htp) $@; \
#       else \
#         rm -rf $(@:.html=.htp); exit 1; \
#       fi
$(srcdir)/doc/interpreter/version-octave.texi: 
$(srcdir)/doc/interpreter/stamp-vti
$(srcdir)/doc/interpreter/stamp-vti: doc/interpreter/octave.texi
$(top_srcdir)/configure


and I can verify that is the case by observing in the Makefile.in file:


@address@hidden/interpreter/octave.dvi:
doc/interpreter/octave.texi $(srcdir)/doc/interpreter/version-octave.texi
doc/interpreter/$(am__dirstamp)
@AMCOND_BUILD_DOCS_FALSE@       
$(AM_V_TEXI2DVI)TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS"
\
@AMCOND_BUILD_DOCS_FALSE@       MAKEINFO='$(MAKEINFO) $(AM_MAKEINFOFLAGS)
$(MAKEINFOFLAGS) -I doc/interpreter -I $(srcdir)/doc/interpreter' \
@AMCOND_BUILD_DOCS_FALSE@       $(TEXI2DVI) $(AM_V_texinfo)
--build-dir=$(@:.dvi=.t2d) -o $@ $(AM_V_texidevnull) \
@AMCOND_BUILD_DOCS_FALSE@       `test -f 'doc/interpreter/octave.texi' || echo
'$(srcdir)/'`doc/interpreter/octave.texi


So, something is indicating that octave.dvi should not be created.  Whether
that is a missing TeX file or something, I will investigate.  However, the
issue is that because octave.dvi is conditionally excluded from the build,
then too should the

TEXI2DVI doc/interpreter/octave.dvi

that attempts to utilize the octave.dvi be excluded.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51911>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/