From: Thiago Jung Bauermann via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 51252@debbugs.gnu.org
Cc: Ricardo Wurmus <rekado@elephly.net>,
John Kehayias <john.kehayias@protonmail.com>,
Robin Templeton <robin@terpri.org>
Subject: bug#51252: [core-updates-frozen] lualatex needs additional setup
Date: Mon, 22 Nov 2021 22:40:01 -0300 [thread overview]
Message-ID: <3440649.fVeeSc1VS3@popigai> (raw)
In-Reply-To: <87r1cf9xl9.fsf@elephly.net>
Hello,
I did some investigation about this problem today. Sorry for the trouble.
Em quarta-feira, 20 de outubro de 2021, às 18:45:35 -03, Ricardo Wurmus escreveu:
> “texlive-latex-base” provides that file. We disable a whole bunch
> of formats that we cannot build that early in the process, and
> then we run fmtutil-sys on the patched file.
> The cause for trouble lies in texlive-kpathsea, which provides
> share/texmf-dist/web2c/fmtutil.cnf
> . That file states how to build the various fmt files.
>
> The file in the earlier version of Tex Live contains this line for the
> lualatex format:
>
> lualatex luatex language.dat,language.dat.lua lualatex.ini
>
> the new file (on core-updates-frozen) says this:
>
> lualatex luahbtex language.dat,language.dat.lua lualatex.ini
>
> i.e. it will try to build the lualatex fmt file with luahbtex
> instead of luatex.
Thank you for this analysis!
> I suppose at this point in the build we don’t
> actually have a working luahbtex, so fmtutil-sys doesn’t generate
> the correct lualatex.fmt.
Looking at the build log of ‘texlive-latex-base’ from the core-updates-
frozen branch, LuaHBTeX seems to be functional at the time it is used to
generate ‘lualatex.fmt’. Comparing it to the build log of the same package
on master, there are some differences though:
• core-updates-frozen shows the following messages:
• “No file TS1lmr.fd.”
• “No file latex2e-first-aid-for-external-files.ltx.”
• core-updates-frozen lists some fonts with strange names and sizes:
• \font\c__fp_exp_intarray=cmr10 at 0.00002pt
• \font\c__fp_trig_intarray=cmr10 at 0.00003pt
• \font\g__regex_state_active_intarray=cmr10 at 0.00005pt
• \font\g__regex_thread_info_intarray=cmr10 at 0.00006pt
• \font\g__regex_submatch_prev_intarray=cmr10 at 0.00008pt
• \font\g__regex_submatch_begin_intarray=cmr10 at 0.00009pt
• \font\g__regex_submatch_end_intarray=cmr10 at 0.0001pt
• \font\g__regex_balance_intarray=cmr10 at 0.00012pt
• master instals file at web2c/luatex/lualatex.fmt, while
core-updates-frozen installs it at web2c/luahbtex/lualatex.fmt.
This last difference coupled with the following excerpt from the TexLive
news section¹:
“LuaTeX: Integration with HarfBuzz library, available as new engines
luahbtex (used for lualatex) and luajithbtex.”
suggests that the command ‘lualatex’ is supposed to invoke the LuaHBTeX
engine rather than the LuaTeX engine. Indeed, when using LuaHBTeX
explicitly, there’s no error about the format file. Unfortunately, there’s an
error about font loading:
--8<---------------cut here---------------start------------->8---
popigai ⸤env⸥: luahbtex '&lualatex' hello.tex
This is LuaHBTeX, Version 1.13.0 (TeX Live 2021/GNU Guix)
restricted system commands enabled.
(./hello.tex
LaTeX2e <2020-10-01> patch level 4
L3 programming layer <2021-02-18> (/gnu/store/nx4jih5xnm6hzfgvi04w4wkp4pbma8bm-profile/share/texmf-dist/tex/latex/base/article.cls
Document Class: article 2020/04/10 v1.4m Standard LaTeX document class
(/gnu/store/nx4jih5xnm6hzfgvi04w4wkp4pbma8bm-profile/share/texmf-dist/tex/latex/base/size10.clo
luaotfload | db : Font names database not found, generating new one.
luaotfload | db : This can take several minutes; please be patient.
luaotfload | db : Reload initiated (formats: otf,ttf,ttc); reason: File not found: "lmroman10-regular".
! Font \TU/lmr/m/n/10=[lmroman10-regular]:+tlig; at 10pt not loadable: metric data not found or bad.
<to be read again>
relax
l.54 \normalsize
?
--8<---------------cut here---------------end--------------->8---
I tried running `luaotfload-tool --update` as suggested on the interwebs
for a similar problem, but I ran into a separate issue with that tool:
--8<---------------cut here---------------start------------->8---
popigai ⸤env⸥: luaotfload-tool --update
...ih5xnm6hzfgvi04w4wkp4pbma8bm-profile/bin/luaotfload-tool:183: module 'alt_getopt' not found:
no field package.preload['alt_getopt']
[kpse lua searcher] file not found: 'alt_getopt'
[kpse C searcher] file not found: 'alt_getopt'
popigai ⸤env⸥:
--8<---------------cut here---------------end--------------->8---
--
Thanks,
Thiago
¹ https://tug.org/texlive/doc/texlive-en/texlive-en.html#news
prev parent reply other threads:[~2021-11-23 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 15:25 bug#51252: [core-updates-frozen] lualatex needs additional setup John Kehayias via Bug reports for GNU Guix
2021-10-17 16:05 ` John Kehayias via Bug reports for GNU Guix
2021-10-17 16:05 ` Robin Templeton
2021-10-20 21:45 ` Ricardo Wurmus
2021-11-23 1:40 ` Thiago Jung Bauermann via Bug reports for GNU Guix [this message]
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=3440649.fVeeSc1VS3@popigai \
--to=bug-guix@gnu.org \
--cc=51252@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
--cc=john.kehayias@protonmail.com \
--cc=rekado@elephly.net \
--cc=robin@terpri.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).