From: luigi scarso <luigi.scarso@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Installing on arm64
Date: Wed, 10 Jun 2020 23:06:01 +0200 [thread overview]
Message-ID: <CAG5iGsDHBh+H36TME1BhVMLxjQxW+M9hCbnfe2yY3og6Cwu91g@mail.gmail.com> (raw)
In-Reply-To: <e440e21c-7944-d20a-ee07-9c19396ccde3@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1073 bytes --]
On Wed, Jun 10, 2020 at 9:07 PM Hans Hagen <j.hagen@xs4all.nl> wrote:
> On 6/10/2020 7:47 PM, luigi scarso wrote:
> >
> >
> > On Wed, Jun 10, 2020 at 7:27 PM Hans Hagen <j.hagen@xs4all.nl
> > <mailto:j.hagen@xs4all.nl>> wrote:
> >
> > On 6/10/2020 7:07 PM, Lutz Haseloff wrote:
> > > I think, there is simply no rule for aarch64 in install.sh
> > >
> > > I now patched it in a better way.
> >
> > ok
> >
> > > The binaries for aarch64 work like a charm on my device, a Samsung
> > > Galaxy A50 Smartphone.
> > Does that really work well? I suppose the cpu and mem is ok, but how
> > about the disk. How do you edit on such a device?
> >
> >
> > doable from years already...
> > use termux
> > https://play.google.com/store/apps/details?id=com.termux&hl=it
> > to run and compile,
> > to cross-compile you need to setup a tool chain for android using ndk.
> sure, i remember running a binary on the nexus made by harald years ago
> but i think i had to root the device first
>
no need to root the device with termux.
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 1905 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-06-10 21:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 8:53 Sytse Knypstra
2020-06-10 9:49 ` Hans Hagen
2020-06-10 10:17 ` Lutz Haseloff
2020-06-10 11:39 ` Hans Hagen
2020-06-10 17:07 ` Lutz Haseloff
2020-06-10 17:27 ` Hans Hagen
2020-06-10 17:47 ` luigi scarso
2020-06-10 19:06 ` Hans Hagen
2020-06-10 21:06 ` luigi scarso [this message]
2020-06-10 18:05 ` Lutz Haseloff
2020-06-11 18:00 ` Lutz Haseloff
2020-06-10 20:14 ` Sytse Knypstra
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=CAG5iGsDHBh+H36TME1BhVMLxjQxW+M9hCbnfe2yY3og6Cwu91g@mail.gmail.com \
--to=luigi.scarso@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).