0

As already reported on this other question I can't write on file 'foo.aux', when:

  1. Using the --output-directory option of both pdflatex and latexmk
  2. Using Tex Live 2017 on Linux

The output directories are not created, i.e., if my directory structure is the following:

  1. thesis/beforetext
  2. thesis/aftertext
  3. thesis/chapters

And I use the option latexmk or pdflatex --output-directory=cache, the following directories are not going to be created by latexmk or pdflatex and the compilation will fail with the errors I can't write on file 'thesis/cache/chapters/chapter1.aux'.

While running pdflatex or latexmk on Windows 10 with MiKTeX-TeX 2.9.6300 everything works fine and the directories thesis/cache/chapters, etc are going to be created correctly and automatically by Miktex.

This only does not work on Linux with TeX 3.14159265 (TeX Live 2017/Debian).

Can I report this nasty bug for TeX Live on Linux somewhere?

Or this is an intended behavior for TeX Live on Linux?

Or is this already reported?

  • Personally, I would expect TeX not to create arbitrary directories (even if only nested). But I can't say whether this is intended. Before reporting a bug you should definitely check if it happens with the most recent versions (TL19) as well. – TeXnician Apr 15 at 5:12
2

This not a bug, you should specify an existing directory

tex --help

reports:

-output-directory=DIR   use existing DIR as the directory to write files in
                            ^^^^^^^^

While this particular case isn't a bug, the answer to the question in the title on where to report texlive bugs is answered on the page https://www.tug.org/texlive/bugs.html

  • Doing tex --help on Miktex shows -output-directory=DIR Use DIR as the directory to write output files to. But the problem is not only the cache directory itself, but all the nested directories which also needs to be created. The biggest issue is how it fails silently, without showing any errors when you run pdflatex --interaction=nonstopmode or batchmode – user Apr 15 at 11:04
  • @user it isn't a silent fail it says it can't write to that location, which is true if it doesn't exist. (on texlive at least) – David Carlisle Apr 15 at 11:07
  • It did not say it cannot write to that location if you pass pdflatex --interaction=nonstopmode or batchmode. I only saw that this was the problem when I removed the pdflatex --interaction=nonstopmode or batchmode. – user Apr 15 at 11:08
  • Then, the question stills, where can I report this behavior for fixing? Linux users do not even think this is a problem? This is a very horrible behavior for user experience. – user Apr 15 at 11:09
  • @user it can not write the log so there is nowhere for it to write the message if you suppress the terminal output. – David Carlisle Apr 15 at 11:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.