ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with Standalone
Date: Wed, 15 Jan 2014 14:47:43 +0100	[thread overview]
Message-ID: <CALBOmsYUuTvUvkDBt5BtCPm8fGos=9WYwyBxRpmp1jmxc9dX1w@mail.gmail.com> (raw)
In-Reply-To: <20140115141716.2120@binki>

On Wed, Jan 15, 2014 at 6:17 AM, Henman wrote:
>
> I am trying to load the standalone but have ran into a problem.
>
> Platform:  cygwin on Windows XP
>
> Here is what I did to try to get it all loaded and setup:
>
> #1 rsync -av rsync://contextgarden.net/minimals/setup/first-setup.sh .
>    sh ./first-setup.sh  || exit 3
>
> The following files are loaded:
>   receiving incremental file list
>         bin/
>         bin/cygiconv-2.dll
>         bin/cygwin1.dll
>         bin/kpathsea620.dll
>         bin/lua52.dll
>         bin/luatex.dll
>         bin/mtx-update.lua
>         bin/mtxrun.dll
>         bin/mtxrun.exe
>         bin/mtxrun.lua
>         bin/rsync.exe
>         bin/texlua.exe
>
>
>     When you want to use context, you need to initialize the tree by typing:
>
>     . /opt/context/tex/setuptex
>
> NOTE: there is no /opt/context/!!  It doesn't get loaded.
>
>
> Any ideas of what is wrong?  Any work around to get the proper tex directory contents?

We used to have cygwin-specific binaries, but dropped them after the
volunteer who built them has lost the interest.

Actually I would surprised if the distribution worked with cygwin
out-of-the-box now that those binaries have been removed (probably a
few years ago already) because we never tried to adapt any code, but I
guess that Akira's native windows binaries should work just as well
under cygwin's shell, so fixing this should be doable.

There are two steps involved in syncronisation. The script
first-setup.sh first determines the platform. In the good old days we
used:

    # cygwin
    CYGWIN*)
        case "$cpu" in
            i*86) platform="cygwin" ;;
            x86_64|ia64) platform="cygwin-64" ;;
            *) platform="unknown" ;;
        esac ;;

and recently switched to:

    CYGWIN*)
        case "$cpu" in
            i*86) platform="mswin" ;; # cygwin, if we ever get "native
cygwin binaries"
            x86_64|ia64) platform="mswin" ;; # cygwin-64, likewise
            *) platform="unknown" ;;
        esac ;;

The script then fetches files from
    rsync -rlptv rsync://contextgarden.net/minimals/setup/$platform/bin .
which apparently succeeds, but then the following step fails:

    mtxrun --script ./bin/mtx-update.lua --force --update
--context=beta --platform=$platform --texroot="$CONTEXTROOT" $@

If this step actually ever worked, it might be that Hans' recent fixes
to determine whether Windows is 64-bit or not, might have broken the
functionality.

In any case I'm almost sure that mtxrun fails to deliver proper
binaries. Is there really no other output to be seen?

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
___________________________________________________________________________________


  parent reply	other threads:[~2014-01-15 13:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15  5:17 Henman
2014-01-15  6:56 ` hwitloc
2014-01-15  9:05   ` Hans Hagen
2014-01-15 11:06     ` hwitloc
2014-01-15 12:39       ` Hans Hagen
2014-01-16  9:23         ` hwitloc
2014-01-16 16:29           ` Hans Hagen
2014-01-15 13:47 ` Mojca Miklavec [this message]
2014-01-16  9:20   ` hwitloc
2014-01-16 10:34     ` Mojca Miklavec

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='CALBOmsYUuTvUvkDBt5BtCPm8fGos=9WYwyBxRpmp1jmxc9dX1w@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).