#2014 Tools/Commands/PDFLaTeX doesn't work fine

None
fixed
nobody
None
1
5 days ago
2017-01-07
Anonymous
No

My system: Windows 8.1 + TeX Live 2016 + TXS 2.12.0

Do the next steps:

Options / Configure TeXstudio / Build / Default Compiler: Latexmk / OK
Wizards / Quick Start / OK
Tools / Commands / PDFLaTeX

Then latexmk runs and not pdflatex!

Discussion

  • Jan  Sundermeyer

    Jan Sundermeyer - 2017-01-07

    looks rather like a set-up problem on your side (options/command)

     
  • hair-splitter

    hair-splitter - 2017-01-07

    I use a "virgin" set-up! Before using the texstudio.ini was deleted. So I don't think that it is a set-up problem.

     
  • Tim Hoffmann

    Tim Hoffmann - 2017-01-07

    What's the exact pdflatex command at Options Commands?
    What's the output on the Messages panel?

     
  • hair-splitter

    hair-splitter - 2017-01-07

    pdflatex command:
    pdflatex.exe -synctex=1 -interaction=nonstopmode %.tex

    the output:

    Process started: latexmk -pdf -silent -synctex=1 "texstudio_zF4856"

    Latexmk: Run number 1 of rule 'pdflatex'

    Latexmk: Log file says no output from latex

    Latexmk: For rule 'pdflatex', no output was made

    Latexmk: Run number 2 of rule 'pdflatex'

    Latexmk: Log file says no output from latex

    Latexmk: For rule 'pdflatex', no output was made

    Failure to make 'texstudio_zF4856.pdf'

    Collected error summary (may duplicate other messages): pdflatex: failed to create output file Latexmk: Use the -f option to force complete processing, unless error was exceeding maximum runs of latex/pdflatex.

    C:\texlive\2016\bin\win32\runscript.tlu:679: command failed with exit code 12: perl.exe c:\texlive\2016\texmf-dist\scripts\latexmk\latexmk.pl -pdf -silent -synctex=1 texstudio_zF4856

    Process exited with error(s)

    Process started: bibtex.exe "texstudio_zF4856"

    This is BibTeX, Version 0.99d (TeX Live 2016/W32TeX)
    The top-level auxiliary file: texstudio_zF4856.aux
    I found no \citation commands---while reading file texstudio_zF4856.aux
    I found no \bibdata command---while reading file texstudio_zF4856.aux
    I found no \bibstyle command---while reading file texstudio_zF4856.aux
    (There were 3 error messages)

    Process exited with error(s)

    Process started: latexmk -pdf -silent -synctex=1 "texstudio_zF4856"

    Latexmk: Run number 1 of rule 'pdflatex'

    Latexmk: Log file says no output from latex

    Latexmk: For rule 'pdflatex', no output was made

    Failure to make 'texstudio_zF4856.pdf'

    Collected error summary (may duplicate other messages): pdflatex: failed to create output file Latexmk: Use the -f option to force complete processing, unless error was exceeding maximum runs of latex/pdflatex.

    C:\texlive\2016\bin\win32\runscript.tlu:679: command failed with exit code 12: perl.exe c:\texlive\2016\texmf-dist\scripts\latexmk\latexmk.pl -pdf -silent -synctex=1 texstudio_zF4856

    Process exited with error(s)

    Process started: pdflatex.exe -synctex=1 -interaction=nonstopmode "texstudio_zF4856".tex

    Process exited normally

     
  • Jan  Sundermeyer

    Jan Sundermeyer - 2017-01-07

    the messages indicate that pdflatex runs and latexmk fails.
    Again, looks like set-up problem with texlive. txs only start the programs...

     
  • Jan  Sundermeyer

    Jan Sundermeyer - 2017-01-07

    and if indeed latexmk fails and not pdflatex, make sure that bpth perl.exe and tl/bin/win32 are part of PATH (or added search path in txs)

     
  • hair-splitter

    hair-splitter - 2017-01-07

    There isn't any problem with texlive. TXS2.11.2 works fine. This bug is only in TXS 2.12.0.

     
  • hair-splitter

    hair-splitter - 2017-01-07

    Please try the next steps:

    Options / Configure TeXstudio / Build / Default Compiler: Latexmk / OK
    Wizards / Quick Start / OK
    Tools / Commands / PDFLaTeX

     
  • hair-splitter

    hair-splitter - 2017-01-12

    In my opinion, this bug causes the following incident, too:

    (System: TXS 2.12.0 with original texstudio.ini, I didn't change anything in it.)

    Type this:

    \documentclass{article}
    \begin{document}
    text
    \end{document}

    Then

    Tools / Commands / XeLaTeX (or LuaLaTeX)

    The bug:

    pdflatex runs and not XeLaTeX or LuaLaTeX!

    I think it is very discomposing effect.

    Remark: The second compilation works fine. (I don't understand, why?)

     
  • Jan  Sundermeyer

    Jan Sundermeyer - 5 days ago

    assume fixed

     
  • Jan  Sundermeyer

    Jan Sundermeyer - 5 days ago
    • status: open --> fixed
    • Group: -->
     
  • Jan  Sundermeyer

    Jan Sundermeyer - 5 days ago

    assuming it is the bibtex call

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks