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>
Subject: Re: Three problems with ConTeXt standalone for armhf
Date: Fri, 19 Jan 2018 08:33:20 +0100	[thread overview]
Message-ID: <CAG5iGsAEQYnv4_Qx_b-qqoGm_YTdEDngN16qTpjnEdJ0eogpEQ@mail.gmail.com> (raw)
In-Reply-To: <8764E7C6-63CD-4BE9-9EFD-CFAA24F8D70C@toppkieker.info>

On Fri, Jan 19, 2018 at 8:31 AM, Lutz Haseloff
<lutz.haseloff@toppkieker.info> wrote:
> Hi all,
>
> 1. the luatex binary for linux armhf is too old for the recent version of
> ConTeXt.
> It is a 1.0.3 from March 2017.
>
> 2. first problem would be not a so big one, but since development level 6505
> I'm not
> able to compile the experimental luatex myself anymore. It compiles
> luajittex but not luatex.
>
> My call to build.sh is: sh ./build.sh --jit --parallel 1>compile.log
> 2>error.log
>
> I append the error.log.
>
> 3. In first-setup.sh is an entry for armv7l. On my system, "uname -m" shows
> armv8l.
> After every download of the script, I have to edit it.
> If someone adds a section for armv8l, I could use the original
> first-setup.sh without changing armv7l to armv8l.
>
>
> Greetings Lutz

looking into it now

-- 
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2018-01-19  7:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19  7:31 Lutz Haseloff
2018-01-19  7:33 ` luigi scarso [this message]
2018-01-19  8:02   ` luigi scarso
2018-01-19 11:54     ` Lutz Haseloff

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=CAG5iGsAEQYnv4_Qx_b-qqoGm_YTdEDngN16qTpjnEdJ0eogpEQ@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).