Re: [Bug-AUCTeX] 2005-06-09; `make' tries to run texi2dvi now on Windows

[David Kastrup]

Christian Schlauer <address@hidden> writes:

> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen.
>
> If the bug (or problem) is triggered by a specific (La)TeX
> file, you should try to produce a minimal sample file showing the
> problem and include it in your report.
>
> Your bug report will be posted to the AUCTeX bug reporting list.
>
> I have problems during `make' in the doc directory, see below. This is
> with a snapshot from Reiner's page.
>
> ,----[ ./configure --prefix=e:/emacs --disable-preview ]
> | checking whether make sets $(MAKE)... yes
> | checking for a BSD-compatible install... /usr/bin/install -c
> | checking for date in ChangeLog... 2005-06-09
> | checking for release in ChangeLog... not found, using 2005-06-09
> instead

I don't think we have had relevant changes since then.  There is the
entry

2005-06-09  Ralf Angeli  <address@hidden>

[...]

        * Makefile.in (DESCEND): Make MSYS happy if $(subdirs) is null,
        e.g. when --disable-preview is used.
        Make the change more safe with regard to the exit code.

But I _think_ it is not relevant.

> | checking for emacs... e:/emacs/bin/emacs
> | checking if e:/emacs/bin/emacs is XEmacs... no
> | checking for Emacs prefix... "e:/emacs"
> | checking if Emacs is recent enough... yes
> | checking for mule support... yes
> | checking if build directory is valid... yes
> | checking where lisp files go... e:/emacs/site-lisp
> | checking what file to use for auctex startup... e:/emacs/site-lisp/auctex.el
> | checking where the package lisp files go... e:/emacs/site-lisp/auctex
> | checking where the data files go... e:/emacs/site-lisp/auctex
> | checking where the info files go... ${prefix}/info
> | checking where automatically generated global style hooks go... 
> ${localstatedir}
> | /auctex
> | checking for tex... /cygdrive/f/miktex/texmf/miktex/bin/tex
> | checking for pdftex... /cygdrive/f/miktex/texmf/miktex/bin/pdftex
> | checking for dvips... /cygdrive/f/miktex/texmf/miktex/bin/dvips

Uh oh.  I hate those kind of magic paths.  Are they just specific for
your Cygwin Shell, or are they also visible from, say, within Emacs if
you do

C-h v exec-path RET

?  If they are, this looks some potential cause for trouble.

> | checking for makeinfo... /usr/bin/makeinfo
> | checking for texi2html... :
> | checking for texi2dvi... /usr/bin/texi2dvi
> | checking for texi2pdf... /usr/bin/texi2pdf
> | checking for install-info... /usr/bin/install-info
> | configure: creating ./config.status
> | config.status: creating Makefile
> | config.status: creating tex-site.el.out
> | config.status: creating doc/Makefile
> | config.status: creating auctex.el
> | 
> | Congratulations!  Configuration is complete.
> | 
> | Type "make" at the prompt to build AUCTeX
> `----
>
> ,----[ make ]
> | 
> | [...]
> | 
> | Wrote i:/auctex/auctex-20050610-a/style/jsbook.elc
> | Wrote i:/auctex/auctex-20050610-a/style/babel.elc
> | Done
> | (cd doc ; make auctex)
> | make[1]: Entering directory `/cygdrive/i/auctex/auctex-20050610-a/doc'
> | /usr/bin/texi2dvi auctex.texi
> | This is e-TeX, Version 3.141592-2.2 (MiKTeX 2.4)
> | entering extended mode
> | ! I can't find file `\cygdrive\i\auctex\auctex-20050610-a\doc\auctex.texi'.
> | <*> .../i/auctex/auctex-20050610-a/doc/auctex.texi
> | 
> | Please type another input file name:
> `----

This means that the Makefile fires in order to generate auctex.dvi
from auctex.texi.  I don't think that the normal run of "make" should
produce a dvi file.  We don't install dvi files as part of the tree,
and so we should not create it.  If we chose to have it as part of the
regular installation, then it should already be present in the
tarball premade, like auctex.info is.  So this would appear to be a
bug in the targets.

I'll take a look at how to fix this.

Thanks for the report.

> So it tries to use `/usr/bin/texi2dvi', which is Cygwin, but then
> MiKTeX enters the scene, and things get messed up!?

You'll likely experience problems with this combination of executables
and paths elsewhere, anyway, but the AUCTeX installation from an
_unmodified_ tarball should not depend on it.

> I think this is the first time that make tries to do something in
> the doc directory. I think before it didn't try to run
> `texi2dvi'.

texi2dvi likely not, but it might be that it ran makeinfo at some
time.  But with the current development sources, it should really not
run anything from the makeinfo/texi2* category unless you touch the
sources or use specific Makefile targets.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum