ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Simon Dales <simon@getthingsfixed.co.uk>, Boris Veytsman <borisv@lk.net>
Subject: Re: standalone / setuptex on ARM
Date: Tue, 23 Aug 2016 13:30:26 +0200	[thread overview]
Message-ID: <CAG5iGsATgVsSsVF6U1tHB4iomaGMyYJBqTi6A-KB-4NnapG8rQ@mail.gmail.com> (raw)
In-Reply-To: <CALBOmsYSmKGHrvL+-su1pAgaJo9Pso=-UgD9xM0iob2UE2WYeQ@mail.gmail.com>

On Tue, Aug 23, 2016 at 12:53 PM, Mojca Miklavec
<mojca.miklavec.lists@gmail.com> wrote:
> On 23 August 2016 at 12:03, Mojca Miklavec wrote:
>> On 23 August 2016 at 11:15, Mojca Miklavec wrote:
>>>
>>> I'll apply the patch. Now, setuptex is not problematic, the same patch
>>> goes there. But mtxrun doing its own guesswork on top of this might
>>> be. Let's see.
>>
>> Can you please try to fetch first-setup.sh again and try to reinstall
>> ConTeXt? You should get LuaTeX beta-0.90.0 r5889 which is a bit old,
>> but just to check whether things work at all. If Luigi plans to make a
>> new release today, it makes no sense to rebuild the binary now
>> (building might take longer than waiting for a new release :)
>
> OK, so Hans' RPi returns (among others):
>
> $ readelf -A /proc/self/exe
>   Tag_CPU_name: "6"
>   Tag_CPU_arch: v6
>   Tag_THUMB_ISA_use: Thumb-1
>   Tag_FP_arch: VFPv2
>   Tag_ABI_HardFP_use: SP and DP
>   Tag_ABI_VFP_args: VFP registers
>
> and the Android by Lutz returns:
>
> $ readelf -A /proc/self/exe
>   Tag_CPU_name: "7-A"
>   Tag_CPU_arch: v7
>   Tag_THUMB_ISA_use: Thumb-2
>   Tag_FP_arch: VFPv3-D16
>   Tag_ABI_HardFP_use: SP and DP
>   Tag_ABI_VFP_args: VFP registers
>
> So his platform gets recognised as armhf and uses the binaries
> compiled on RPi, but it gives strange results.
>
> Lutz, I suggest you come to the ConTeXt Meeting (train ticket to
> Zwolle costs just 29-39 EUR) and don't let Luigi & Philipp away from
> their keybords until your problem gets fixed :) :) :)

I wonder if we have to consider Android instead of ARM.


-- 
luigi
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2016-08-23 11:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23  5:46 Philipp Gesang
2016-08-23  8:44 ` Hans Hagen
2016-08-23  9:15   ` Mojca Miklavec
2016-08-23  9:27     ` Mojca Miklavec
2016-08-23 10:03     ` Mojca Miklavec
2016-08-23 10:53       ` Mojca Miklavec
2016-08-23 11:30         ` luigi scarso [this message]
2016-08-23 17:41     ` Philipp Gesang

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=CAG5iGsATgVsSsVF6U1tHB4iomaGMyYJBqTi6A-KB-4NnapG8rQ@mail.gmail.com \
    --to=luigi.scarso@gmail.com \
    --cc=borisv@lk.net \
    --cc=ntg-context@ntg.nl \
    --cc=simon@getthingsfixed.co.uk \
    /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).