From: Jose Luis Arellano <jose.4rellano@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt on linux-armhf
Date: Mon, 8 Aug 2016 16:42:41 -0300 [thread overview]
Message-ID: <CABLfLbCKn6Eofr81Hiij4ADJkfm0w0VkJhqojEHZbVj_abF-Vg@mail.gmail.com> (raw)
In-Reply-To: <CABLfLbAf6ecTGi4Mu_gbn205fykmCgy2CboODNAL4fgSPN0otQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 4333 bytes --]
I have performed a clean installation of ConTeXt Standalone beta and when i
try to compile i get this:
error loading file: lang-txt.lua (aborting)
mtx-context | error, no format found with name: cont-en, aborting
2016-08-08 16:16 GMT-03:00 Jose Luis Arellano <jose.4rellano@gmail.com>:
> Well, if i use the binary from http://tug.org/svn/
> texlive/trunk/Master/bin/armel-linux/ (Revision 41089) i get "Segmentation
> fault".
> However, the binary from http://tug.org/svn/texlive/trunk/Master/bin/
> armhf-linux/ (Revision 41117) seems to work perfectly fine.
> Thanks guys.
>
> 2016-08-08 5:14 GMT-03:00 Henri Menke <henrimenke@gmail.com>:
>
>> Hi,
>>
>> as far as I know, there is no such thing like the standard ARM chip. The
>> ARM company designs chips to fit the needs of their customers. Therefore,
>> the Raspberry Pi processor and the processor in a smartphone may have a
>> very different instruction set.
>>
>> The Wikipedia page for the ARM Cortex-A7 (Raspberry Pi 2 Model B) lists
>> several other chips implementing the Cortex-A7 instruction set. I would
>> only guarantee compatibility with these chips if the binaries were built
>> for this architecture.
>>
>> https://en.wikipedia.org/wiki/ARM_Cortex-A7
>>
>> Another issue I could think of is the filesystem format. This is very
>> heterogeneous among Android vendors. I think Samsung uses f2fs, HTC uses
>> YAFFS, and LG uses ext4. It could be that the luatex binary runs on some
>> kind of compatibility layer within Android which is either lacking correct
>> filesystem syscalls or is doing them wrong.
>>
>> These are just ideas. I hope it helps anyway.
>> Cheers, Henri
>>
>> On 08/08/2016 09:46 AM, Mojca Miklavec wrote:
>> > On 8 August 2016 at 06:53, Jose Luis Arellano wrote:
>> >> Hi Mojca,
>> >>
>> >> The binaries comes from armhf (your build), as you can see in logs
>> attached.
>> >> While the version of Tex Live installed is texlive-bin-2016.41290-5-
>> armv7h.
>> >
>> > armv7h looks like "armhf".
>> >
>> > But I checked the logs and you are most likely using the binaries that
>> > were compiled for Arch Linux and your machine (CPU) specifically
>> > rather than the ones that are compiled by the TeX Live team.
>> >
>> > Can you try replacing the luatex binary in ConTeXt distribution with
>> > the binaries from
>> > http://tug.org/svn/texlive/trunk/Master/bin/
>> > please try once with armel-linux/luatex and once with
>> > armhf-linux/luatex. (You can fetch the binary via SVN or via viewvc,
>> > but make sure that the downloaded file will be executable.)
>> >
>> > I'm curious whether that binary works for you (try with armhf-linux
>> first).
>> >
>> >> Maybe the problem is related to architecture of cpu, the latest
>> raspbian use
>> >> ARMv8.
>> >
>> > The exact architecture depends on hardware rather than software. I
>> > guess we have RPi2 B (Hans must know). For some reason I cannot access
>> > the machine at the moment, but I guess that RPi2+ is also armv7 (ARM
>> > Cortex-A7). I'm not 100% sure though.
>> >
>> > The question is whether an older version of OS would help in any way.
>> >
>> > In any case you should be able to just copy the luatex from your
>> > distro to the minimals and get a working PDF.
>> >
>> > 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/list
>> info/ntg-context
>> > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
>> > archive : http://foundry.supelec.fr/projects/contextrev/
>> > wiki : http://contextgarden.net
>> > ____________________________________________________________
>> _______________________
>> >
>>
>> ____________________________________________________________
>> _______________________
>> 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/list
>> info/ntg-context
>> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
>> archive : http://foundry.supelec.fr/projects/contextrev/
>> wiki : http://contextgarden.net
>> ____________________________________________________________
>> _______________________
>>
>
>
[-- Attachment #1.2: Type: text/html, Size: 6909 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-08-08 19:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 22:19 Jose Luis Arellano
2016-08-05 22:44 ` Mojca Miklavec
2016-08-05 22:54 ` Jose Luis Arellano
2016-08-07 3:31 ` Jose Luis Arellano
2016-08-07 8:21 ` Pablo Rodriguez
2016-08-07 12:14 ` Mojca Miklavec
2016-08-08 4:53 ` Jose Luis Arellano
2016-08-08 7:46 ` Mojca Miklavec
2016-08-08 8:14 ` Henri Menke
2016-08-08 19:16 ` Jose Luis Arellano
2016-08-08 19:42 ` Jose Luis Arellano [this message]
2016-08-08 20:29 ` Hans Hagen
2016-08-08 23:09 ` Mojca Miklavec
2016-08-30 0:51 ` Jose Luis Arellano
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=CABLfLbCKn6Eofr81Hiij4ADJkfm0w0VkJhqojEHZbVj_abF-Vg@mail.gmail.com \
--to=jose.4rellano@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).