From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Failure building standalone
Date: Fri, 21 Jun 2013 09:54:56 +0200 [thread overview]
Message-ID: <8A88259F-2711-4A09-A31C-3D45C860A859@web.de> (raw)
In-Reply-To: <CALBOmsbNvgr5sOysBv0bYhQNq5DQEbrpMeWjHtiT6c1gg=Dzzg@mail.gmail.com>
Hi All, Mojca,
please excuse my ignorance of the inner workings of windows, but
would it not be possible to have the permissions corrected by the first-setup.sh
script after the rsync?
regards
Keith.
Am 21.06.2013 um 07:56 schrieb Mojca Miklavec <mojca.miklavec.lists@gmail.com>:
> On Thu, Jun 20, 2013 at 6:39 PM, <hwitloc@gmail.com> wrote:
>>
>> Thanks Mojca. Re-running the command today got me a little further. Thank you.
>>
>> The problem encounted now is:
>>
>> --------------------------------
>> sh ./first-setup.sh --modules=all --engine=luatex --context=current
>> receiving incremental file list
>>
>> sent 64 bytes received 322 bytes 85.78 bytes/sec
>> total size is 10993585 speedup is 28480.79
>> env: mtxrun: Permission denied
>>
>> --------------------------------
>>
>> I explicity set the permissions to allow me execute access, but script fails toward the end.
>> But, it looks lke the sh script itself is chaning the perameters. Or else my setup is intentionally tricking me.
>
> Unless you comment out the part of first-setup.sh which syncs
> ./bin/mtxrun.exe, the file is going to be overwritten each time and
> the file on server wasn't executable (because it usually doesn't make
> any difference for windows users anyway).
>
> I fixed the executable bits on server. Please try again.
>
> (But please note that when we user rsync as provided by rsync in past,
> binaries were broken even if the executable bit was set on the server.
> We had to use "set cygwin nontsec" or something like this to overcome
> the problem, or run chmod after each sync. I hope that you won't be
> bitten by this, but we were.)
>
> Mojca
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-06-21 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 13:18 hwitloc
2013-06-20 13:34 ` Mojca Miklavec
2013-06-20 16:39 ` hwitloc
2013-06-21 5:56 ` Mojca Miklavec
2013-06-21 7:54 ` Keith J. Schultz [this message]
2013-06-21 9:16 ` Mojca Miklavec
2013-06-21 11:11 ` Keith J. Schultz
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=8A88259F-2711-4A09-A31C-3D45C860A859@web.de \
--to=keithjschultz@web.de \
--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).