From: Paul Menzel <paulepanter@users.sourceforge.net>
To: ntg-context@ntg.nl
Subject: Minimals/MTXrun: 32-bit system with 64-bit kernel: `MTXrun | no 'texmf-linux-64'`
Date: Mon, 24 Jan 2011 02:13:07 +0100 [thread overview]
Message-ID: <1295831587.7645.48.camel@mattotaupa> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2209 bytes --]
Dear ConTeXt folks,
I am running a 32-bit system with a 64-bit kernel. So relying on
uname -m
to determine the architecture leads to problems [1].
So I do `cpu = "i686` manually in `first-setup.sh` but I still do get
the the following error message.
sent 1145 bytes received 8908331 bytes 774737.04 bytes/sec
total size is 31230200 speedup is 3.51
MTXrun | mtx update: updating mtxrun for linux: rsync -tgo --chmod=a+x /opt/context/tex/texmf-context/scripts/context/lua/mtxrun.lua /opt/context/tex/texmf-linux/bin/mtxrun
MTXrun | run: rsync -tgo --chmod=a+x /opt/context/tex/texmf-context/scripts/context/lua/mtxrun.lua /opt/context/tex/texmf-linux/bin/mtxrun
→ MTXrun | no 'texmf-linux-64' under tree /opt/context/tex
When you want to use context, you need to initialize the tree by typing:
. /opt/context/tex/setuptex
`first-setup.sh` executes the following command
# download or update the distribution
# you may remove the --context=beta switch if you want to use "current"
mtxrun --verbose --script ./bin/mtx-update.lua --update --make --force --engine=all --context=beta --platform=$platform --texroot=$PWD/tex $@
but `mtxrun` or `mtx-update.lua` does not seem to honor the option `--platform` all the way.
I tried to even hardcode `platform` to `linux` in `mtxrun` but it does not help.¹
elseif name == "linux" then
function os.resolvers.platform(t,k)
-- we sometims have HOSTTYPE set so let's check that first
local platform, architecture = "", os.getenv("HOSTTYPE") or os.resultof("uname -m") or ""
if find(architecture,"x86_64") then
platform = "linux-64"
elseif find(architecture,"ppc") then
platform = "linux-ppc"
else
platform = "linux"
end
os.setenv("MTX_PLATFORM",platform)
os.platform = platform
→ return "linux"
end
Could you please tell me, where the path for the `texmf` directory is determined and how I can force that to a certain platform.
Thanks,
Paul
[1] http://tug.org/pipermail/tex-live/2009-June/021119.html
[2] http://tug.org/pipermail/tex-live/2009-June/021124.html
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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 reply other threads:[~2011-01-24 1:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 1:13 Paul Menzel [this message]
2011-01-24 1:50 ` Aditya Mahajan
2011-01-24 21:54 ` Paul Menzel
2011-01-25 0:18 ` Aditya Mahajan
2011-01-25 1:00 ` Paul Menzel
2011-01-25 8:35 ` Hans Hagen
2011-01-26 2:58 ` 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=1295831587.7645.48.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--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).