-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
build conflict with texlive-latex-base (Ubuntu 11.10) #1692
Comments
Works for me on Ubuntu 12.04
|
That's a newer version than in 11.10, apparently:
This is actually working for you after running ./configure again after installing |
Sorry, can you clarify:
Thanks. |
Specifically, this is the error (more):
Running that command on its own fails, as well, and there are no PDFs created in the doc folder:
This is with pandoc 1.8.1.1 and the rust.tex file here... |
If you remove the -interaction=batchmode flag you'll get a ... plausibly more informative, or at least "more verbose" TeX-ese error. Can I get the output from that? |
Ping. Can you check provide further details? |
So, I'd forgotten @lht's comment, and upgraded to Ubuntu 12.04 (beta2) before coming to read this again. Since I seem to be the only one to have noticed this issue, I'm comfortable just closing this: 12.04 is going to be fully released in just a few days... Except I have another issue with 12.04. :P There's no obvious error, but although the /doc/rust.pdf is created, it is almost empty! //sigh |
I spoke too soon. Installing node.js (the bog standard version in Ubuntu's repository) fixed that. The docs look fine in 12.04. |
Ok. So .. closing this, I guess? Reopen if you feel something's still amiss. |
So, I can reproduce this, on Ubuntu 12.10: ! LaTeX Error: File `lmodern.sty' not found. |
'apt-set install lmodern' corrects it for me. |
@rbtcollins That looks like a different error to me so I opened #3989 for it. Thanks! |
I've found that with Ubuntu 11.10's
texlive-latex-base
package installed, I can'tmake
.After removing it and reconfiguring, things are OK again...
The text was updated successfully, but these errors were encountered: