all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou via Guix-patches via <guix-patches@gnu.org>
To: Jorge Acereda <jacereda@gmail.com>
Cc: 71602@debbugs.gnu.org
Subject: [bug#71602] [PATCH] gnu: texlive-scripts: add mktexfmt
Date: Sun, 30 Jun 2024 19:10:42 +0200	[thread overview]
Message-ID: <87ed8e8igd.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CADhgfdpHQ3Rs7hJ42GAWnL0cjem67gZOvd2Sn4=ZY8Zucvm+dg@mail.gmail.com> (Jorge Acereda's message of "Sun, 30 Jun 2024 18:47:20 +0200")

Jorge Acereda <jacereda@gmail.com> writes:

> On Sun, Jun 30, 2024 at 4:32 PM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> This is rather surprising. "mktexfmt" is not directly used to compile
>> documents, but rather to create format files. However, these format
>> files are pre-generated during build, without relying on "mktexfmt".
>>
>> Also, I can export from Org to LaTeX without issues. Your problem lies
>> elsewhere, IMO. Maybe an incomplete TeX Live installation ?
>>
>
> Oh, sorry. I mean org-latex-export-to-pdf. Maybe I'm missing something
> as you suggest. I have installed  texlive-bin, texlive-etex and
> texlive-scripts. This is what I'm getting:
>
> This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023/GNU
> Guix) (preloaded format=pdflatex)
>  restricted \write18 enabled.
>
> kpathsea: Running mktexfmt pdflatex.fmt
> mktexfmt: No such file or directory
> I can't find the format file `pdflatex.fmt'!

I see.

The first thing to know is the error above is a red herring. Formats
(i.e. ".fmt" files) are pre-generated when TeX Live packages are built.
When kpathsea library does not find one, it tries to generate it with
"mktexfmt", but the problem stems from the fact that you didn't install
the package containing the expected format in the first place. In this
case, the package texlive-latex-bin does provide it.

Anyway, the packages "texlive-bin, texlive-etex and texlive-scripts" are
clearly insufficient to compile any document. As indicated in the
manual, you should install collections of packages to create
a self-sufficient TeX Live distribution. For Org, at the very least, you
should start by installing texlive-collection-latexrecommended (and
remove the previous packages you had). The packages
texlive-collection-pictures (for PGF/TikZ) and
texlive-collection-fontsrecommended can be nice to have, too, but they
are optional for Org.

However, if you want a relatively small TeX Live installation, you may
want to stay away from texlive-collection-binextra,
texlive-collection-fontsextra, texlive-collection-fontutils, and
texlive-collection-latexextra, which can be quite large. I suggest to
pick the individual packages you need from them. Off the top of my head,
for Org, you may want:

- texlive-capt-of
- texlive-soul
- texlive-ulem
- texlilve-wrapfig

all from texlive-collection-latexextra.

Of course, if space is not an issue, installing
texlive-collection-latexextra (roughly 1500 packages, 1G) is an option.
There is also texlive-scheme-full (schemes are meta packages mixing
collections and sometimes individual packages), which installs all TeX
Live (4500 packages, 4G). But I really recommend to spend a few minutes
to select a sufficient TeX Live tree instead.

HTH,

Regards,
-- 
Nicolas Goaziou






  reply	other threads:[~2024-06-30 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16 19:08 [bug#71602] [PATCH] gnu: texlive-scripts: add mktexfmt spencerpeters via Guix-patches via
2024-06-17  7:18 ` bug#71602: " Nicolas Goaziou via Guix-patches via
2024-06-30 11:34 ` [bug#71602] " Jorge Acereda
2024-06-30 14:32   ` Nicolas Goaziou via Guix-patches via
2024-06-30 16:47     ` Jorge Acereda
2024-06-30 17:10       ` Nicolas Goaziou via Guix-patches via [this message]
2024-06-30 17:49         ` Jorge Acereda

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ed8e8igd.fsf@nicolasgoaziou.fr \
    --to=guix-patches@gnu.org \
    --cc=71602@debbugs.gnu.org \
    --cc=jacereda@gmail.com \
    --cc=mail@nicolasgoaziou.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.