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