ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Error: your system "Linux aarch64" is not supported yet.
Date: Fri, 27 Sep 2019 07:19:50 +0200	[thread overview]
Message-ID: <CALBOmsYNW3vjfTbv=wgRccooGXro55FZxYAeizGv1WHjdmB3mQ@mail.gmail.com> (raw)
In-Reply-To: <CAG5iGsAmk9kujFjUzo1ErURq_2OrN+g9-jehmOOZn5iPMwAYbQ@mail.gmail.com>

On Fri, 27 Sep 2019 at 00:49, luigi scarso <luigi.scarso@gmail.com> wrote:
>
> ..but aarch is in texlive already from  while ...

Having it in TL is usually not sufficient, we should usually be able
to build it ourselves to get the latest version of luatex etc. (But I
could use the binaries from TL as a starting point.)

That's either cross-compiling, but probably easier to simply put some
proper hardware in place, so that we can also run the test suite.

I was thinking of getting hold of another Raspberry and trying to
install a 64-bit system on it. Or maybe dig out my super old Pine64
and build on that one. Nobody ever asked for binaries, so we were not
in a hurry.

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2019-09-27  5:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 22:49 luigi scarso
2019-09-27  5:19 ` Mojca Miklavec [this message]
2019-09-27  6:13   ` luigi scarso

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='CALBOmsYNW3vjfTbv=wgRccooGXro55FZxYAeizGv1WHjdmB3mQ@mail.gmail.com' \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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).