From: Alan Braslau <alan.braslau@cea.fr>
To: Pablo Rodriguez <oinos@gmx.es>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: a question on setuptex
Date: Fri, 17 Feb 2017 15:46:43 -0700 [thread overview]
Message-ID: <20170217154643.241f5917@zoo.hsd1.co.comcast.net> (raw)
In-Reply-To: <5ba29f5d-c78a-c744-5e98-cb6be66485ee@gmx.es>
On Fri, 17 Feb 2017 23:38:09 +0100
Pablo Rodriguez <oinos@gmx.es> wrote:
> 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.
The script relies on "unamne -m". It does not care what processor is
used, but rather what system and libraries are installed. You can
certainly run the 32bit binaries in a 32bit chroot (but why would you
want to do this?).
Alan
___________________________________________________________________________________
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:46 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 [this message]
2017-02-17 22:49 ` Mojca Miklavec
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=20170217154643.241f5917@zoo.hsd1.co.comcast.net \
--to=alan.braslau@cea.fr \
--cc=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).