--- Begin Message ---
|
Subject: |
Modular texlive has problems finding fonts |
|
Date: |
Mon, 03 Jan 2022 17:18:01 +0100 |
As discussed on #guix on IRC, several folks including myself ran into
issues getting the following some-file.tex:
--8<---------------cut here---------------start------------->8---
\documentclass[11pt]{article}
\begin{document}
Hello friends
\end{document}
--8<---------------cut here---------------end--------------->8---
... to typeset with the following manifest.scm:
--8<---------------cut here---------------start------------->8---
(specifications->manifest
'("texlive-base"
"texlive-fonts-ec"
"texlive-amsfonts"
"texlive-fira"
"texlive-inconsolata"))
--8<---------------cut here---------------end--------------->8---
... with command:
`guix shell --pure coreutils grep sed gawk -m manifest.scm -- pdflatex some-file
Note that the monolithic texlive seems to work:
`guix shell --pure coreutils grep sed gawk texlive -- pdflatex some-file'
On IRC, rekado /w strace identified that texlive does not seem to be
entering the subdirectory containing the font files, as it seems to be
loading texlive-bin's texmf.cnf, instead of the one generated by
`(@ (guix profiles) texlive-configuration)'.
It seems some of the talks in the guix-maintenance repository can
currently also not be built for the same or similar reason.
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#52979: Modular texlive has problems finding fonts |
|
Date: |
Tue, 04 Jan 2022 15:28:17 +0100 |
|
User-agent: |
mu4e 1.6.10; emacs 27.2 |
Ricardo Wurmus <rekado@elephly.net> writes:
> So, two things to do here:
>
> 1) patch mktexpk, mktexnam, mktexnam.opt,
> share/texmf-dist/web2c/mktexupd, et al to find “sed” and “awk”.
Done.
> 2) figure out why pdflatex tries to use bitmap fonts at all when other
> files exist.
Not done, but the problem has gone away after fixing the former problem.
This now works on wip-texlive, which I just pushed.
--
Ricardo
--- End Message ---