unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: 49218-done@debbugs.gnu.org
Subject: bug#49218: texlive-latex-base fails to build: "missing engine: luajithbtex"
Date: Tue, 06 Jul 2021 21:08:30 -0700	[thread overview]
Message-ID: <87fswqvk8x.fsf@gmail.com> (raw)
In-Reply-To: <87bl7u5yu1.fsf@gmail.com> (Chris Marusich's message of "Thu, 24 Jun 2021 22:36:26 -0700")

[-- Attachment #1: Type: text/plain, Size: 2494 bytes --]

Hi,

I've committed the patch as 68b0e0d511c2873603636e9f783ff59aac4b7612 on
core-updates.  I'm closing this bug report.

Chris Marusich <cmmarusich@gmail.com> writes:

> - Will LuaJIT ever support the powerpc64le architecture?  Until it does,
>   I guess we can't use LuaJIT on powerpc64le at all, not just for
>   TeX-related stuff.

See: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=49220

In short, it does not seem like upstream support for powerpc64le is
forthcoming in the near future.  But maybe that will change with time.

> - Is it correct to add "mfluajit" to the disabled-formats list, like I
>   do in my patch?  It sounds like "mfluajit" is a related to "metafont",
>   but I don't yet really understand what that means.  Is it an engine
>   like luajit?  Is it correct to include mfluajit in the list of formats
>   to disable in fmtutil.cnf when running fmtutil-sys?  I am totally
>   unfamiliar with these tools, so I have no idea.  Perhaps it makes no
>   sense to include mfluajit here, even if maybe it is benign to do so.
>   If any TeX wizards out there can clarify this for me, I'd be happy to
>   adjust the patch as needed.

FYI, I found this information about formats and engines:

https://www.tug.org/levels.html

According to that document, "engines" are "executable binaries which
implement different TeX variants", and "formats" are "the TeX-based
languages in which one actually writes documents".  The config file
contains lines like this:

  # from lollipop:
  lollipop tex - lollipop.ini
  #
  # from luatex:
  luatex luatex language.def,language.dat.lua luatex.ini
  dviluatex luatex language.def,language.dat.lua dviluatex.ini
  luajittex luajittex language.def,language.dat.lua luatex.ini
  #
  # from metafont:
  mf mf-nowin - -translate-file=cp227.tcx mf.ini

It looks to me like it's fine to include "mfluajit" in the
disabled-formats list.  Clearly, some metafont "formats" and "engines"
are included in this config file already.  That said, adding "mfluajit"
to the list does nothing right now, since the config file doesn't
actually contain any lines beginning with the word "mfluajit", anyway.
And in any case, if "mfluajit" ever does get added to the config file
somehow, then surely we would want to disable it for powerpc64le-linux,
since LuaJIT is not currently supported on that platform.  Therefore, I
think it's correct to include "mfluajit" in the disabled-formats list.

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

      reply	other threads:[~2021-07-07  4:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25  5:36 bug#49218: texlive-latex-base fails to build: "missing engine: luajithbtex" Chris Marusich
2021-07-07  4:08 ` Chris Marusich [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=87fswqvk8x.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=49218-done@debbugs.gnu.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).