On Mon, Jan 24, 2011 at 02:13, Paul Menzel wrote:
> 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].
I am aware of that. At the moment it is a bit nasty since --platform
is not favo
On 25-1-2011 2:00, Paul Menzel wrote:
1. Could there be some corrupted caches which need to be deleted? I
reinstalled everything by deleting `/opt/context`. But maybe something
was left over from the broken installation beforehand?
2. How can I update ConTeXt Minimals without getting `setuptex`
Am Montag, den 24.01.2011, 19:18 -0500 schrieb Aditya Mahajan:
> On Mon, 24 Jan 2011, Paul Menzel wrote:
>
> >MTXrun | run: rsync -rpztlv --delete
> > contextgarden.net::'minimals/current/base/tex/
> > minimals/current/base/metapost/ minimals/current/fonts/common/
> > minimals/current/f
On Mon, 24 Jan 2011, Paul Menzel wrote:
MTXrun | run: rsync -rpztlv --delete
contextgarden.net::'minimals/current/base/tex/
minimals/current/base/metapost/ minimals/current/fonts/common/
minimals/current/fonts/other/ minimals/current/misc/web2c
minimals/current/base/xetex/ minimals/cur
Am Sonntag, den 23.01.2011, 20:50 -0500 schrieb Aditya Mahajan:
> On Mon, 24 Jan 2011, Paul Menzel wrote:
> > 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
On Mon, 24 Jan 2011, Paul Menzel wrote:
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 me
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 8
