From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: Publish to PDF on Linux: An impossible task? Date: Sun, 10 Nov 2019 18:54:24 -0600 Message-ID: References: <87ftiv5joy.fsf@mbork.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:46739) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iTxyX-0007Gy-OO for emacs-orgmode@gnu.org; Sun, 10 Nov 2019 19:54:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iTxyW-0006Ph-C0 for emacs-orgmode@gnu.org; Sun, 10 Nov 2019 19:54:37 -0500 Received: from mail-qt1-x832.google.com ([2607:f8b0:4864:20::832]:36494) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iTxyW-0006Pa-8Y for emacs-orgmode@gnu.org; Sun, 10 Nov 2019 19:54:36 -0500 Received: by mail-qt1-x832.google.com with SMTP id y10so13926105qto.3 for ; Sun, 10 Nov 2019 16:54:36 -0800 (PST) In-Reply-To: <87ftiv5joy.fsf@mbork.pl> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Marcin Borkowski Cc: emacs-orgmode On Sun, Nov 10, 2019 at 6:41 PM Marcin Borkowski wrote: > > > On 2019-11-11, at 01:25, John Hendy wrote: > > > On Sun, Nov 10, 2019 at 6:01 PM Nathan Neff wro= te: > >> > >> After using org-mode for 10 years, I run for the doorway when > >> I even think about trying to convert an org-mode file to PDF. > >> > >> *** I quiver when I see errors such as: > >> > >> warning: kpathsea: configuration file texmf.cnf not found in these dir= ectories: /usr/bin:/usr/bin/share/texmf-local/web2c:/usr/bin/share/texmf-di= st/web2c:/usr/bin/share/texmf/web2c:/usr/bin/texmf-local/web2c:/usr/bin/tex= mf-dist/web2c:/usr/bin/texmf/web2c:/usr:/usr/share/texmf-local/web2c:/usr/s= hare/texmf-dist/web2c:/usr/share/texmf/web2c:/usr/texmf-local/web2c:/usr/te= xmf-dist/web2c:/usr/texmf/web2c://texmf-local/web2c:/://share/texmf-local/w= eb2c://share/texmf-dist/web2c://share/texmf/web2c://texmf-local/web2c://tex= mf-dist/web2c://texmf/web2c. > >> This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch Lin= ux) (preloaded format=3Dpdflatex) > >> > >> kpathsea: Running mktexfmt pdflatex.fmt > >> mktexfmt: No such file or directory > >> I can't find the format file `pdflatex.fmt'! > > > > These look like latex errors to me, nothing to do with Org. Guessing > > These are not LaTeX errors, they are lower-level ones. By "LaTeX" I mean "that which is necessary to have a functioning latex system." If by lower-level you mean the ecosystem itself vs. compiling errors, completely agree. Clearly some core components are missing. For example, the texmf.cnf file is provided by the arch package texlive-core (assuming a package was used), so that's potentially not even installed. - https://www.archlinux.org/packages/extra/any/texlive-core/ > > you used the arch package? I'm on arch myself, but after getting > > bitten by package mismatches and things being hopelessly broken, I > > switched to just using texlive directly: > > - https://www.tug.org/texlive/ > > > > It's not that bad. There's even a quick guide to walk you through the > > tl-install script. If you'd rather troubleshoot what you have going on > > now, here's some places to start: > > - you're missing files... figure out which package is supposed to > > provide them and install it > > He misses LaTeX format file itself, and apparently mktexfmt (which > should create it) cannot be found. This seems more serious than what > you write. I would divide "serious" into "major but simple" and "complicated." In easily 90% of cases with error output like this, it's going to be a missing package, not some intricate system glitch that requires troubleshooting. Indeed, my guess is exactly that: there are "serious" errors because nothing resembling a functioning latex system exists. The root cause is probably very simple. > > - check your paths > > Agreed, but this may be quite subtle... Again, I suspect much simpler. When using texlive directly, for example, one has to set paths correctly. This If it's looking in system paths vs. a user path (e.g. I install to ~/.texlive, not /usr) and this was not set via .bashrc, that's what I mean one should check. This presumes the expected packages are installed at all. I would start with simply: $ pacman -Q |grep tex and $ which pdflatex John > > Best, > > -- > Marcin Borkowski > http://mbork.pl