On 2025-07-16 11:25, Pat Pannuto <[email protected]> wrote: > I'm surprised you are seeing multiple reads to test.tex from one invocation > of pdftex, at least with pdflatex as a driver, you have to explicitly call > the command multiple times.
I also tested it running pdftex under strace, and there were multiple reads (even for the one pdftex pass). But I don't think that the multiple reads are causing the problem with tup. For I also use context (another tex cousin), which does the multiple passes on its own reading the .tex file (at least) once each time, and it works fine with tup. So it may be a subtle interaction between pdftex and fuse? (I also had the same problem with pdflatex.) > Tup isn't okay with multiple build rules modifying the same output > file, so you have to have one single tup command do all of the (la)tex > driver invocations, i.e., here's the relevant snippet from a paper > from 2016: Ah, that's good to know. For latex, you could solve the problem by using latexmk. It does all the rerunning with interleaved bibtexing. It's very useful for Makefiles (and, once this issue is solved, Tupfiles). I'm going to try "tup --debug-fuse" to see if I get any clues there. Best, -Sanjoy -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/tup-users/87ldon3nym.fsf%40mit.edu.
