ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jeong Dal <haksan@me.com>
To: Otared Kavian <otared@gmail.com>
Cc: "list ntg-context@ntg.nl ntg-context@ntg.nl ntg-context@ntg.nl
	ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Re: problem with a new installation of LMTX
Date: Mon, 9 Dec 2019 10:03:12 +0900	[thread overview]
Message-ID: <33DB2AF0-11AF-4170-90B0-663C0E44ADD5@me.com> (raw)
In-Reply-To: <F146037B-D750-407F-AA4F-37D9410A4F27@gmail.com>

Dear Otared,

Thank you for the zip file.
I downloaded it and copied it in a folder.
(There is no context-cache folder in the zip file)
In the terminal, I run “mtxrun —generate” and “context —make”.
But system doesn’t allow the execution of “luametatex”.
So I open the system preference:security part, and clear and allow the running “luametatex”.
But the system hinders “luametatex” continuously.

I have to ask about it to MAC service first to resolve this problem.
If it is not working after the resolve security problem, I may go back to previous version of OSX.
I’ll let you know the progress.

Thank you again.

Best regards,

Dalyoung
 

> 2019. 12. 9. 오전 6:34, Otared Kavian <otared@gmail.com> 작성:
> 
> Dear Dalyoung,
> 
> I made a zip file of the context-osx-64 tree on my machine, and put it on Dropbox
> 	https://www.dropbox.com/s/6isogxi78fwp1se/context-osx-64.zip?dl=0
> for you: you can try to install it on your Mac running MacOS 10.15 Catalina. Could you please tell me if you succeed to implement the procedure I described in the other email?
> 
> Best regards: OK
> 
>> On 8 Dec 2019, at 13:31, Jeong Dal <haksan@me.com> wrote:
>> 
>> For test, I  installed again after removing ConTeXtLMTX folder.
>> But it is same as before.
>> 
>> I looked files in “/tex/texmf-osx-64/bin”.
>> There are 5 files: context, context.lua, luametatex, mtxrun, mtxrun.lua.
>> context and mtxrun are symbolic linked to luametatex.
>> But luametatex is not executable, so I changed it using “chmod 755 luametatex”.
>> I run “mtxrun —generate”, then it set variables as follows:
>> 
>> % mtxrun --generate
>> resolvers       | resolving | variable 'SELFAUTOLOC' set to '/usr/local/texlive/2019/bin/x86_64-darwin'
>> resolvers       | resolving | variable 'SELFAUTODIR' set to '/usr/local/texlive/2019/bin'
>> resolvers       | resolving | variable 'SELFAUTOPARENT' set to '/usr/local/texlive/2019'
>> resolvers       | resolving | variable 'TEXMFCNF' set to ''
>> resolvers       | resolving | variable 'TEXMF' set to ''
>> resolvers       | resolving | variable 'TEXOS' set to 'bin'
>> resolvers       | resolving |
>> …….
>> 
>> and do many things in the texlive/2019 folders.
>> 
>> My question is that luametatex is distributed as  an inexecutable form deliberately?
>> 
>> Thank you for reading.
>> 
>> Best regards,
>> 
>> Dalyoung
>> 
>> 
>> 
>> 
>> ___________________________________________________________________________________
>> 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
>> ___________________________________________________________________________________
> 

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

  parent reply	other threads:[~2019-12-09  1:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.231.1575790766.1207.ntg-context@ntg.nl>
2019-12-08  8:12 ` Jeong Dal
2019-12-08  9:48   ` Floris van Manen
2019-12-08 11:15   ` Otared Kavian
2019-12-08 16:35     ` Alan Braslau
2019-12-08 17:00       ` Floris van Manen
2019-12-08 20:02       ` Mojca Miklavec
2019-12-08 12:31 ` Jeong Dal
     [not found]   ` <F146037B-D750-407F-AA4F-37D9410A4F27@gmail.com>
2019-12-09  1:03     ` Jeong Dal [this message]
     [not found]       ` <35D60F4E-5B50-43AA-9934-A1BF52FF68B2@gmail.com>
     [not found]         ` <97B7FB7E-AF9A-478E-BD68-A01E988E4FF0@me.com>
2019-12-09 14:57           ` problem with a new installation of LMTX: Solved! Otared Kavian
     [not found] <mailman.1.1575716401.11346.ntg-context@ntg.nl>
2019-12-07 14:11 ` problem with a new installation of LMTX Jeong Dal
2019-12-07 15:16   ` Hans Hagen
2019-12-07 23:20     ` Jeong Dal
2019-12-07 23:35       ` Hans Hagen
2019-12-08 16:30         ` Alan Braslau
2019-12-09  1:03           ` Jeong Dal
2019-12-08 20:07         ` Mojca Miklavec
2019-12-08  7:08       ` Otared Kavian
2019-12-08  7:36         ` Richard Mahoney | Indica et Buddhica
     [not found]           ` <dcf18d57-eeb1-41b8-28b0-1a9c518e4250@xs4all.nl>
2019-12-08 18:12             ` Richard Mahoney | Indica et Buddhica
2019-12-07 15:44   ` Otared Kavian
2019-12-07 19:39     ` Hans Hagen
2019-12-07 21:01       ` Otared Kavian

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=33DB2AF0-11AF-4170-90B0-663C0E44ADD5@me.com \
    --to=haksan@me.com \
    --cc=ntg-context@ntg.nl \
    --cc=otared@gmail.com \
    /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).