From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: Install problem on aarch64
Date: Thu, 23 Jan 2025 09:35:29 +0100 [thread overview]
Message-ID: <76257ee2-b7a7-4bcb-9cc8-39a9b60db3bd@freedom.nl> (raw)
In-Reply-To: <CA+9XOxpXARxvGgwF--XJ372CVEHPZZPx1R5om6ujPVpdzchWNw@mail.gmail.com>
On 1/23/2025 8:25 AM, Christian Prim via ntg-context wrote:
> Hi everyone
>
> Fresh install today on a new computer. I get this error during the
> install process and after an attempted update:
>
> loading > ConTeXt Spacing Macros / Horizontal
> resolvers > lua > loading file '/home/christian/context/tex/texmf-
> context/tex/context/base/mkxl/spac-hor.lmt' succeeded
> tex error > tex error on line 34 in file spac-hor.mkxl: Undefined
> control sequence
>
> <line 3.34>
> \bitwiseflip \normalizeparmode \removetrailingspacesnormalizeparcode
>
> <empty file>
> The control sequence at the end of the top line of your error message
> was never
> \def'ed. You can just continue as I'll forget about whatever was undefined.
> resolvers | formats |
> resolvers | formats | binary path : /home/christian/context/
> tex/texmf-linux-aarch64/bin
> resolvers | formats | format path : /home/christian/context/
> tex/texmf-cache/luametatex-cache/
> context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex
> resolvers | formats | luatex engine : luametatex
> resolvers | formats | lua startup file : /home/christian/context/
> tex/texmf-context/tex/context/base/mkxl/luat-cod.lmt
> resolvers | formats | context file : /home/christian/context/
> tex/texmf-context/tex/context/base/mkxl/cont-en.mkxl
> resolvers | formats | run time : 2.498 seconds
> resolvers | formats | return value : error
> resolvers | formats |
> system | total runtime: 2.760 seconds of 2.881 seconds
>
> I can't generate the needed cont-en format file for context to work.
>
> Is that a known problem? Am I missing something? I don't think it is
> related to the aarch64 architecture. But who knows...
>
> Thanks for your help!
The aarch 64 buiuld is a bit ragile because it runs on a vm on an arm
mac that has timing issues and occasionally drops off line, so it can be
that we have an old (or bad) binary occasionally.
You can try to compile yourself (just run the build script in the source
tree and move the binaries to the right spot afterwards).
I'll probably update one of these days anyway,
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
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2025-01-23 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 7:25 [NTG-context] " Christian Prim via ntg-context
2025-01-23 8:35 ` Hans Hagen via ntg-context [this message]
2025-01-23 11:07 ` [NTG-context] " Christian Prim via ntg-context
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=76257ee2-b7a7-4bcb-9cc8-39a9b60db3bd@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).