From: Claudio Di Vita <claudio.divita-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: M1 support for Docker image
Date: Thu, 24 Nov 2022 04:12:42 -0800 (PST) [thread overview]
Message-ID: <39b0a0ad-5bc0-488c-ba00-5f75fe25c949n@googlegroups.com> (raw)
In-Reply-To: <87fse9pub8.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2767 bytes --]
I updated the Dockerfile for ubuntu replacing the PATH assignment in the
following way:
# TeXLive binaries location
ARG texlive_bin="/opt/texlive/texdir/bin"
RUN TEXLIVE_ARCH="$(uname -p)-$(uname -s | tr '[:upper:]' '[:lower:]')" && \
mkdir -p ${texlive_bin} && \
ln -sf "${texlive_bin}/${TEXLIVE_ARCH}" "${texlive_bin}/default"
# Modify PATH environment variable, prepending TexLive bin directory
ENV PATH="${texlive_bin}/default:${PATH}"
Build args are not useful, because they cannot be changed based on the
architecture, therefore I used a symbolic link to place the right directory
within PATH.
However, I noticed that the directory /usr/share/lua/5.4 is not created
when building the pandoc/core:edge images (that use Lua 5.4), so the module
re.lua is not copied to the host. Is something related to changes
introduced by Lua 5.4 ?
Moreover, while edge images build works, building from 2.19.2 fails.
Can issue a PR for updating the Dockerfile (at least for Ubuntu) to include
the TeXLive path change ?
Cheers,
Claudio
Il giorno mercoledì 23 novembre 2022 alle 16:25:08 UTC+1 Albert Krewinkel
ha scritto:
>
> Claudio Di Vita <claudio...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > With a support of a colleague that has an Apple M1, I'm trying to
> > build the pandoc/latex:edge-ubuntu image.
>
> That's great news!
>
> > The build fails due to some installation issue with TexLive:
> >
> > Time used for installing the packages: 00:38
> > running mktexlsr /opt/texlive/texdir/texmf-dist ...
> > [...]
> > Add /opt/texlive/texdir/texmf-dist/doc/info to INFOPATH.
> > Most importantly, add /opt/texlive/texdir/bin/aarch64-linux
> > to your PATH for current and future sessions.
> > [...]
> >
> > Any clue on the possible cause ?
>
> The problem is that the Dockerfile hard-codes the path for x86-64:
>
> ENV PATH="/opt/texlive/texdir/bin/x86_64-linux:${PATH}"
>
> We could probably add `arch` as another Docker build parameter, or
> otherwise should find a different way to set the path to its correct
> value.
>
> Can you try to modify the line manually to see if the build succeeds
> with
>
> ENV PATH="/opt/texlive/texdir/bin/aarch64-linux:${PATH}"
>
> --
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/39b0a0ad-5bc0-488c-ba00-5f75fe25c949n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3625 bytes --]
prev parent reply other threads:[~2022-11-24 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 19:49 Claudio Di Vita
[not found] ` <CAMBF16tDmPmmBZ96wMug7ebhnHRUjKaNXWY=EWNM2qr9AY7o+g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-10-18 21:15 ` Albert Krewinkel
[not found] ` <87y1tcj0g2.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-10-19 11:14 ` 'Till Grallert' via pandoc-discuss
[not found] ` <ee6644df-f0f3-4dc3-988a-97228c93f1c9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-23 10:33 ` Claudio Di Vita
[not found] ` <4aa8604b-23c8-4960-ba58-d168bee56bfdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-23 15:17 ` Albert Krewinkel
[not found] ` <87fse9pub8.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-24 12:12 ` Claudio Di Vita [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39b0a0ad-5bc0-488c-ba00-5f75fe25c949n@googlegroups.com \
--to=claudio.divita-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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 NNTP newsgroup(s).