-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot "make" PDF #65
Comments
Hey @lacabra. My system is a Debian GNU/Linux recently-updated
What version of From the error above, it looks like maybe pandoc's internal conversion from Markdown->LaTeX is generating invalid LaTeX? (Hence the syntax error about an extra "}", which presumably is in the (La)TeX input to MacTex.) The document is building fine for me with commit e79a27d (current head of |
Thanks @kfogel. I was using an older version it seems: $ pandoc --version
pandoc 2.2.1
Compiled with pandoc-types 1.17.4.2, texmath 0.11, skylighting 0.7.1 I upgraded to the latest available in my system: $ pandoc --version
pandoc 2.16.2
Compiled with pandoc-types 1.22.1, texmath 0.12.3.2, skylighting 0.12.1, citeproc 0.6, ipynb 0.1.0.2 And unfortunately, now I am getting a different error, which I am investigating: $ make
pandoc: pdflatex: createProcess: posix_spawnp: illegal operation (Inappropriate ioctl for device)
make: *** [pdf] Error 1 I confirm that I'm on the latest commit of the |
The previous error is a very cryptic one to say that I managed to make it work with the following: brew install pandoc
brew install basictex
sudo tlmgr update --self
sudo tlmgr install titlesec Now it works just fine, closing (and I will document this elsewhere for future reference). |
Wow! Sorry for the trouble; I'm glad you debugged it all the way. If you want to make a doc PR for CONTRIBUTE.md or the Makefile, I'll happily review it. |
In my local MacOS environment, after having installed MacTex (which provides the LaTEX system that pandoc depends on), I get the following error when running
make
to generate the PDF:Before I attempt to troubleshoot this, it would be good to understand the details of the system where @kfogel has run this successfully.
The text was updated successfully, but these errors were encountered: