ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Keith McKay <mckaymeister@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: arm osx
Date: Fri, 23 Apr 2021 15:45:46 +0100	[thread overview]
Message-ID: <868a66c5-8d7b-e706-c9c5-8d060e05e910@gmail.com> (raw)
In-Reply-To: <C2BF95BC-42F9-494F-8B1C-95E19FF874BB@icloud.com>


[-- Attachment #1.1: Type: text/plain, Size: 4291 bytes --]

Hi Charles

Firstly. I can take no credit for getting Context running on the new M1 
Mac OS ARM. Hans and his team are the real heroes here. I just 
downloaded the zip file and off I went.

I don't normally use TexShop, I use Texworks, but I have it set up on my 
machine. I cant remember how I setup the engine but I checked it out and 
it runs as expected. Here is the engine I use:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

#!/bin/bash

export 
PATH=/Users/pothole/data/contextarm64/tex/texmf-osx-64/bin:/Users/pothole/data/context/tex/texmf-osx-64/bin

/Users/pothole/data/contextarm64/tex/texmf-osx-64/bin/mtxrun 
--autogenerate --script context --autopdf "$1"

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

I did exactly as you did only I unzipped into /data/contextarm64. I did 
this because I have another directory into which I unzipped the intel 
version. It means I have two ConText options, intel and arm. The only 
other differences are my engine is a bash file and I don't remember 
making it executable.

Hope this helps. I'm happy to help off list if you want.

Best Wishes

Keith

On 23/04/2021 12:11, Charles Doherty wrote:
> Hi all (especially Keith who successfully got Context running on the 
> new M1 Mac OS ARM)
>
> Again thanks to Mojca for providing the Mac OS ARM download. I 
> recently replace my old Mac with the new ARM one.
>
> I am having difficulty getting ConTeXt to work.  This is what I have 
> done and the information from the console.
>
> I downloaded:
>
> context-osx-arm64.zip
>
> In terminal:  cd /Users/charlesdoherty/context-osx-arm64
>
> Ran sh install.sh
>
> and all seems ok (following Keith’s advice on privacy).
>
> I made an engine for TeXShop based on what worked before:
>
> #!/bin/Zsh
> export 
> PATH=$PATH:~/context-osx-arm64/bin:~/context-osx-arm64/tex/texmf-osx-64/bin
> ~/context-osx-arm64/tex/texmf-osx-64/bin/mtxrun --autogenerate 
> --script context --directives="system.showerror" --autopdf "$1" --purgeall
>
> I made it executable.
>
> When I typeset a file in TeXShop using this engine I get:
>
> /Users/charlesdoherty/Library/TeXShop/Engines/ARM.engine:3: bad CPU 
> type in executable: 
> /Users/charlesdoherty/context-osx-arm64/tex/texmf-osx-64/bin/mtxrun
>
> I have tried various options to no avail but I would really appreciate 
> some help on this (longhand rather than cryptic would be really helpful).
>
> Thanks,
> Charlie
>
>
>
>> On 11 Apr 2021, at 19:27, Keith McKay <mckaymeister@gmail.com 
>> <mailto:mckaymeister@gmail.com>> wrote:
>>
>> An alternative way is to go to Preferences>>Security and 
>> Privacy>>General. And then click on Open anyway and that's it sorted.
>> Best Wishes
>> Keith
>>
>>
>>
>> On Sun, 11 Apr 2021, 18:47 Otared Kavian, <otared@gmail.com 
>> <mailto:otared@gmail.com>> wrote:
>>
>>     Hi,
>>
>>     Thank you Mojca and Hans for the new binary for MacOS ARM:
>>     yesterday I installed it on my new MacBook Pro ARM and everything
>>     works like a charm.
>>
>>     Just for the persons who run into difficulties when running
>>     sh install.sh
>>     and see that MacOS 11 prevents mtxrun to run properly, in the
>>     Finder you should find the file
>>
>>     context-osx-arm64/bin/mtxrun
>>
>>     and then you press Control while clicking on it. You’ll see a pop
>>     up window, and you choose Open, and when the Finder tells you
>>     whether you really want to open that file, you say YES…
>>     After this, the install script does what it has to do and you
>>     don’t need anymore to authorize mtxrun to run.
>>
>>     Best regards: Otared
>>
>
> *******************************
> CHARLES DOHERTY
> 13 BANCROFT ROAD
> TALLAGHT
> DUBLIN
> D24 YH2V
> home: +353 1 2447483
> Mobile: +353 863868629
> charles.doherty@icloud.com <mailto:charles.doherty@icloud.com>
>
>
>
>
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

[-- Attachment #1.2: Type: text/html, Size: 15938 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2021-04-23 14:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-10 15:21 Hans Hagen
2021-04-11  9:39 ` Keith McKay
2021-04-11 17:47 ` Otared Kavian
2021-04-11 18:27   ` Keith McKay
2021-04-23 11:11     ` Charles Doherty
2021-04-23 14:45       ` Keith McKay [this message]
2021-04-23 14:53         ` Keith McKay
2021-04-25  8:58           ` Charles Doherty
2021-04-25 16:52             ` Keith McKay
2022-05-29 18:35               ` Steffen Wolfrum via ntg-context
2022-05-29 20:15                 ` Keith McKay via ntg-context
2022-05-30  7:06                   ` Taco Hoekwater 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=868a66c5-8d7b-e706-c9c5-8d060e05e910@gmail.com \
    --to=mckaymeister@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).