public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: M1 support for Docker image
Date: Wed, 23 Nov 2022 16:17:39 +0100	[thread overview]
Message-ID: <87fse9pub8.fsf@zeitkraut.de> (raw)
In-Reply-To: <4aa8604b-23c8-4960-ba58-d168bee56bfdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Claudio Di Vita <claudio.divita-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


  parent reply	other threads:[~2022-11-23 15:17 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 [this message]
     [not found]                 ` <87fse9pub8.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-24 12:12                   ` Claudio Di Vita

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=87fse9pub8.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).