From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Minimals Beta on Windows 64bit
Date: Mon, 26 Jul 2010 18:07:24 +0200 [thread overview]
Message-ID: <AANLkTikaHeLBBOMxRUYuFcjG0Oe_CLE5gNFVjH0pF8KO@mail.gmail.com> (raw)
In-Reply-To: <09b0b93efb77c651c86521051c81da9c@localhost>
On Fri, Jul 23, 2010 at 14:04, Andreas Schneider wrote:
>
> Since one of the last Betas mtxrun seems to be aware of 64bit windows, but
> all the stubs and scripts seem to be missing support for that resulting in
> the whole setup to not work at all.
>
> First-setup fails with stuff like that:
> MTXrun | run: rsync -rpztlv --stats
> contextgarden.net::'minimals/current/bin/common/mswin/
> minimals/current/bin/context/mswin/ minimals/current/bin/metapost/mswin/
> minimals/current/bin/man/ minimals/current/bin/luatex/mswin/
> minimals/current/bin/xetex/mswin/ minimals/current/bin/luatex/mswin/
> minimals/current/bin/luatex/mswin/ minimals/current/bin/pdftex/mswin/'
> 'c:/context/tex/texmf-mswin'The source and destination cannot both be
> remote.
> rsync error: syntax or usage error (code 1) at main.c(1127)
> [receiver=3.0.2]
>
> Easy fix: in mtx-update.lua, line 294 the current check is
> if osplatform == "windows" or osplatform == "mswin" then
> which should also check for "mswin-64".
No, we don't have any special 64-bit binaries for windows. So it
should always unconditionally recognize windows as mswin, no matter
whether they are 32- or 64-bit.
> But even after fixing that, mtxrun fails at several points, because it
> tries to run further commands from "tex/texmf-mswin-64".
>
> Another easy fix: add a hardlink/junction for that directory.
> But that only ended in the following error whenever I invoke mtxrun,
> texlua, etc.:
>
> "texlua.exe - Application Error
> The application was unable to start correctly (0xc0000022). click OK to
> close the application."
>
> I don't know why that was changed, but afaik all 64bit versions of windows
> support 32bit too so I would vote to leave it as it was before - just deal
> with mswin-64 as if it was mswin.
The problem is that I'm not able to reproduce the problem you are
reporting. Did anyone else experience the same problem?
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:[~2010-07-26 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 12:04 Andreas Schneider
2010-07-26 16:07 ` Mojca Miklavec [this message]
2010-07-29 11:26 ` Andreas Schneider
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=AANLkTikaHeLBBOMxRUYuFcjG0Oe_CLE5gNFVjH0pF8KO@mail.gmail.com \
--to=mojca.miklavec.lists@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).