From: Ricardo Wurmus <rekado@elephly.net>
To: Marco van Hulten <marco@hulten.org>
Cc: help-guix@gnu.org
Subject: Re: TeX Live issues
Date: Fri, 17 Jan 2020 13:02:57 +0100 [thread overview]
Message-ID: <875zhaxpce.fsf@elephly.net> (raw)
In-Reply-To: <20200117085108.524b637c@jasniac.instanton>
Marco van Hulten <marco@hulten.org> writes:
> Je 17 jan 08:48 skribis Marco:
>> Hi there—
>>
>> I am unable to use LaTeX and friends. I get this error:
>>
>> [...]
>
> and in another profile yet another issue:
>
> ```
> $ pdflatex test
> This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded format=pdflatex)
> restricted \write18 enabled.
>
> kpathsea: Running mktexfmt pdflatex.fmt
> /gnu/store/znf7mmx3vslsscn9v3ilxmgkirqwswy8-texlive-bin-20180414/share/texmf-dist/scripts/texlive/fmtutil.pl: Unexpected non-option argument(s): pdflatex.fmt
> Try "fmtutil --help" for more information.
> I can't find the format file `pdflatex.fmt'!
> ```
This sounds like a search path problem. We are generating all the
common fmt files in texlive-latex-base. So when using the modular LaTeX
this already works fine.
To try the modular LaTeX install at least “texlive-base” into your
profile and remove the monolithic package.
--
Ricardo
next prev parent reply other threads:[~2020-01-17 12:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 7:48 TeX Live issues Marco van Hulten
2020-01-17 7:51 ` Marco van Hulten
2020-01-17 12:02 ` Ricardo Wurmus [this message]
2020-01-17 9:03 ` Ricardo Wurmus
[not found] ` <20200117124027.50e7287d@gfi063209.klientdrift.uib.no>
2020-01-17 12:05 ` Ricardo Wurmus
2020-01-18 15:08 ` Marco van Hulten
2020-01-18 15:12 ` Ricardo Wurmus
2020-01-18 17:29 ` Marco van Hulten
2020-01-19 8:59 ` Ricardo Wurmus
2020-01-19 10:16 ` Marco van Hulten
2020-01-19 13:42 ` Ricardo Wurmus
2020-01-19 14:57 ` Marco van Hulten
2020-01-19 15:01 ` Ricardo Wurmus
2020-01-19 16:34 ` Marco van Hulten
2020-01-19 20:17 ` Marco van Hulten
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zhaxpce.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=marco@hulten.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).