From: Wojtek Kosior via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 64772@debbugs.gnu.org
Subject: bug#64772: TeXlive (specifically LuaLaTeX) has become terribly slow
Date: Fri, 28 Jul 2023 22:33:18 +0200 [thread overview]
Message-ID: <20230728223318.1df4cd3c.koszko@koszko.org> (raw)
In-Reply-To: <87ila41b1x.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]
> Could you try adding a phase doing the following to texlive-luatex?
>
> --8<---------------cut here---------------start------------->8---
> (substitute* (string-append #$output "/share/texmf-dist/web2c/texmfcnf.lua")
> (("selfautodir:") #$output)
> (("selfautoparent:") (string-append #$output "/share/")))
> --8<---------------cut here---------------end--------------->8---
Actually, I've been using the `lualatex` command from the `texlive`
package. I now see I my reports might have been confusing as I didn't
mention that. I apologize :(
Although `lualatex` from `texlive` has been slow for me, now, when
using `guix shell texlive-collection-latex` with guix
76e041f9eef85bb039c5251d3350c62ee2066883, I get a rather satisfactory
time (below 4s on old Lenovo T400) when compiling this test doc
--8<---------------cut here---------------start------------->8---
\documentclass{article}
\title{somedoc}
\begin{document}
aaa
\end{document}
--8<---------------cut here---------------end--------------->8---
These tons of `ENOENT` are still there in strace's output, tho.
Back to your snippet — if you still think it's worth trying (to see if
it gets rid of the ENOENTs), I'll try it and report later.
> The files above are probably generated, and I don't know when.
Although I know a lot less about TeX than you, I can at least say that
they are not actually "needed" — no package in my store (not even the
entire nicely-working texlive from before the merge) had a directory
named "lualatexquotejobname". Neither of the following commands yielded
anything
--8<---------------cut here---------------start------------->8---
find /gnu/store/ -mindepth 1 -maxdepth 1 -name *texlive* -type d -exec find '{}' -name lualatexquotejobname -type d \;
find ~/.texlive2021/ -name lualatexquotejobname -type d
find ~/.texlive2023/ -name lualatexquotejobname -type d
--8<---------------cut here---------------end--------------->8---
> I suggest to drop this "fix" for now.
OK
Best,
Wojtek
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-07-28 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 15:54 bug#64772: TeXlive (specifically LuaLaTeX) has become terribly slow Malte Frank Gerdes
2023-07-26 22:21 ` Wojtek Kosior via Bug reports for GNU Guix
2023-07-27 20:07 ` Wojtek Kosior via Bug reports for GNU Guix
2023-07-28 12:21 ` Nicolas Goaziou
2023-07-28 20:33 ` Wojtek Kosior via Bug reports for GNU Guix [this message]
2023-07-28 21:25 ` Wojtek Kosior via Bug reports for GNU Guix
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=20230728223318.1df4cd3c.koszko@koszko.org \
--to=bug-guix@gnu.org \
--cc=64772@debbugs.gnu.org \
--cc=koszko@koszko.org \
--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 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).