[NTG-context] ConTeXt Standalone does not works on macOS Monterey with Apple M2 chip

Tommaso Gordini illinguista1972 at gmail.com
Mon Oct 10 15:13:13 CEST 2022


Hello Mojca:

uname -a

Darwin MacBook-Air-di-Tommaso.local 21.6.0 Darwin Kernel Version 21.6.0:
Mon Aug 22 20:20:07 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T8110
arm64


uname-m

arm64

Tommaso



Il giorno lun 10 ott 2022 alle ore 08:49 Mojca Miklavec <
mojca.miklavec.lists at gmail.com> ha scritto:

> On Sun, 9 Oct 2022 at 09:24, Tommaso Gordini via ntg-context wrote:
> >
> > Hello list,
> >
> > I'm trying to install ConTeXt Standalone on my Mac (macOS 12.6 Monterey
> and Apple M2 chip) but at the end of the installation the ConTeXt-MkIV
> folder (where I install Standalone) on the disk weighs only 7MB (the tex
> tree is created, but its folders are empty).
> > I've never had a problem installing it on my old computer (Intel
> processor).
> >
> > Do you know if it is a known problem?
>
> It should work, at least in theory. I'll check later today on our M1
> machine.
> If that doesn't work, it should be some trivial problem (that should
> be straightforward to fix).
> If that works, it could be that "uname" reports something different
> than "arm64" on M2. That should hopefully be easy to fix as well.
>
> What does "uname -m" (and "uname -a") report on your mac?
>
> Mojca
>

Il giorno lun 10 ott 2022 alle ore 08:49 Mojca Miklavec <
mojca.miklavec.lists at gmail.com> ha scritto:

> On Sun, 9 Oct 2022 at 09:24, Tommaso Gordini via ntg-context wrote:
> >
> > Hello list,
> >
> > I'm trying to install ConTeXt Standalone on my Mac (macOS 12.6 Monterey
> and Apple M2 chip) but at the end of the installation the ConTeXt-MkIV
> folder (where I install Standalone) on the disk weighs only 7MB (the tex
> tree is created, but its folders are empty).
> > I've never had a problem installing it on my old computer (Intel
> processor).
> >
> > Do you know if it is a known problem?
>
> It should work, at least in theory. I'll check later today on our M1
> machine.
> If that doesn't work, it should be some trivial problem (that should
> be straightforward to fix).
> If that works, it could be that "uname" reports something different
> than "arm64" on M2. That should hopefully be easy to fix as well.
>
> What does "uname -m" (and "uname -a") report on your mac?
>
> Mojca
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ntg.nl/pipermail/ntg-context/attachments/20221010/8d6c63dc/attachment.htm>


More information about the ntg-context mailing list