On 6/10/2020 12:17 PM, Lutz Haseloff wrote:

Hi all,

I got my system working by quick and dirty patching install.sh

I have now

PLATFORM="linux-aarch64"

after the last esac and all works like expected.

I would like to have a check for aarch64 in the install.sh too. you can prototype that and tell what to adapt

----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

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?

(Over the time lmtx became more efficient in terms on memory (access) and such. Compiling the luametatex manual on the RPI 4 (somewhat overclocked) takes 3 times when my laptop does which I consider okay, although the aim of course is less, which is hard because it then also runs faster on the laptop. Not that there's much to gain. The bottleneck is more at the lua end nowadays.) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

On 6/10/2020 7:47 PM, luigi scarso wrote:

On Wed, Jun 10, 2020 at 7:27 PM Hans Hagen 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 Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

I run the "Userland" App from Playstore. That App integrates well with Android. I can edit with vim in the kali linux terminal or with any other Editor for Android like Jota+. I can try to compile the luametatex manual and send you the results. Greetings Lutz Am 10. Juni 2020 19:27:28 MESZ schrieb Hans Hagen :

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?

(Over the time lmtx became more efficient in terms on memory (access) and such. Compiling the luametatex manual on the RPI 4 (somewhat overclocked) takes 3 times when my laptop does which I consider okay, although the aim of course is less, which is hard because it then also runs faster on the laptop. Not that there's much to gain. The bottleneck is more at the lua end nowadays.)

Hans

----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------