From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: a question on setuptex
Date: Fri, 17 Feb 2017 23:49:28 +0100 [thread overview]
Message-ID: <CALBOmsbtcF5_0E353rjCAx7TVahFwvO7Af-6jVm1YRxOdg=n7g@mail.gmail.com> (raw)
In-Reply-To: <5ba29f5d-c78a-c744-5e98-cb6be66485ee@gmx.es>
On 17 February 2017 at 23:38, Pablo Rodriguez wrote:
> Hans,
>
> would it be possible that a 32bit ConTeXt Suite can be used with a 64bit
> architecture in Linux?
>
> Sorry, but yesterday I was surprised to see that setuptex isn’t able to
> find any binaries in Linux if they are 32bit and the processor is 64bit.
>
> Of course, it makes sense in that case that a ConTeXt Suite with 64bit
> binaries is preferred. But as a fallback, 32bit binaries should be fine.
It should work in principle. Just set "platform=linux" before calling
mtx-update.lua and disable '--make'. (You could in principle also call
rsync manually.) And then all you need to do is set the PATH to
binaries.
The problem is that unless something changed, mtxrun will most likely
be causing you some troubles and will insist in fetching x86_64 (I'm
not sure how to completely avoid that).
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-02-17 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 22:38 Pablo Rodriguez
2017-02-17 22:46 ` Alan Braslau
2017-02-17 22:49 ` Mojca Miklavec [this message]
2017-02-18 9:23 ` Hans Hagen
2017-02-18 22:08 ` Pablo Rodriguez
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='CALBOmsbtcF5_0E353rjCAx7TVahFwvO7Af-6jVm1YRxOdg=n7g@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).