yochju / latex-makefile

Automatically exported from code.google.com/p/latex-makefile
Other
0 stars 0 forks source link

TOC not build at the first run of make #64

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi, when I "make" my project the first time, the TOC is not built at all.
Only after "touch"ing my .tex file and call "make" again I get an TOC. The
pdf looks fine, all chapters etc. are there, just the TOC is empty.

I'm using the classicthesis with lots of separate files. The first run
complains like this:

NOTE: You may ignore warnings about the following files:

     Dissertation.d

Makefile:1900: Dissertation.d: No such file or directory
= Dissertation.tex --> Dissertation.d Dissertation.dvi (1) =
= Bibliography.bib Dissertation.aux --> Dissertation.bbl =
I found no \citation commands---while reading file Dissertation.aux
Database file #1: Bibliography.bib

The TOC seems to be always one change (compilation) behind of my changes.

I'm using latex-makefile 2.1.43 on Ubuntu 9.04.

Original issue reported on code.google.com by jakl.mic...@gmail.com on 15 Feb 2010 at 12:59

GoogleCodeExporter commented 9 years ago
"make -B" fixes the problem for now, and reveals that the warning/error that 
I've no
\citation commands in my .aux file is the cause of the trouble. It prevents the 
other
passes of latex to be run.
Currently I've only a skeleton with chapter headings etc., so this won't be an 
issue
for long.

Original comment by jakl.mic...@gmail.com on 15 Feb 2010 at 1:06

GoogleCodeExporter commented 9 years ago
Wait, that's weird.  The TOC shouldn't rely on \citation commands, should it?

By the way, how did you figure out that this was the problem?  I'm always 
looking for 
new sleuthing tricks.  And I'd like to see if I can make this work properly.

Original comment by shiblon on 16 Feb 2010 at 3:08

GoogleCodeExporter commented 9 years ago
The processing stopped after bibtex reported the problem (not immediately, but 
latex
wasn't run anymore), forcing all targets (with make -B) revealed that there 
*should*
be more passes. Now that I made a few references it worked flawlessly.

Unfortunately I've made a few changes and now I'm dependent on pdflatex (the 
same
problem as [issue 55]).

Original comment by jakl.mic...@gmail.com on 16 Feb 2010 at 4:59

GoogleCodeExporter commented 9 years ago
I'm interested on why you are now dependent on pdflatex.  What changes did you 
make 
that introduced that dependency?

Also, I'm not sure, but it seems like this might not be a bug that needs to 
remain 
opened?  Do you think there is something here that needs fixing, or did we run 
into a 
limitation of bibtex?

Original comment by shiblon on 17 Feb 2010 at 3:53

GoogleCodeExporter commented 9 years ago
I'm using classicthesis[1], which doesn't compile with latex. To be fair, only
certain documents can't be compiled with plain latex (mine and the 
documentation of
classicthesis, for example). I've experimented with some parameters for 
hyperref and
graphicx, but had no luck so far.

Simply changing the latex command in the Makefile.ini seems like a hack, or 
would you
recommend it that way?

The issue can be closed we've diverged from the topic anyway, running bibtex 
without
citations should not be a normal use-case.

Cheers,
Michael

 1: http://www.ctan.org/tex-archive/macros/latex/contrib/classicthesis/

Original comment by jakl.mic...@gmail.com on 17 Feb 2010 at 4:46

GoogleCodeExporter commented 9 years ago
Sounds good - closing.

Sorry that it doesn't work with latex.  Changing the LATEX invocation to be 
pdflatex 
is not *likely* to work, but it just might.  Have you tried that?  Did it work?

The trouble with pdflatex is that the makefile really depends on dvi being the 
ultimate output, and on it not being created unless there aren't significant 
errors.   
pdflatex creates a pdf whether there are errors or not, which makes things a 
little 
trickier.

I have this somewhere in my long queue of things to do; I want to try forking 
the 
makefile and making a branch of it work with pdflatex.  If it isn't too 
invasive, I'll then 
try merging them back together in some meaningful way.  Meanwhile, the queue 
continues to grow :-/

Original comment by shiblon on 17 Feb 2010 at 6:25

GoogleCodeExporter commented 9 years ago
I've tried pdflatex, it did work... somehow, yet I'm reverting to something 
else for
this document, for everything else I prefer the makefile (it's just too simple 
not to
use it :)).

Thanks for releasing it, the readable error messages are really worth it.

Original comment by jakl.mic...@gmail.com on 17 Feb 2010 at 10:28

GoogleCodeExporter commented 9 years ago
pdflatex is now supported properly (crossing my fingers, anyway).  Please give 
it a spin.

r26679dd06711 or version 2.2.0-alpha1 from the downloads page.

Original comment by shiblon on 9 Mar 2010 at 8:27

GoogleCodeExporter commented 9 years ago
Works like a charm! Thank you!

Original comment by jakl.mic...@gmail.com on 9 Mar 2010 at 9:22

GoogleCodeExporter commented 9 years ago
Glad to hear it!  Marking verified.  Keep your eyes open for updated versions.  
I'm fixing 
lots of little things now that pdflatex is basically working.

Original comment by shiblon on 10 Mar 2010 at 4:22