ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: strange crash
Date: Thu, 16 Feb 2017 22:20:14 +0100	[thread overview]
Message-ID: <e8f8f0cf-f359-ae92-1485-162f5277db39@gmx.es> (raw)
In-Reply-To: <op.yvrts5kqkcdbg5@muck.fritz.box>

On 02/16/2017 09:56 PM, j. van den hoff wrote:
> [...]
> just to avoid confusion: my initial report concerned x86_64 linux.

I know and you’d have downloaded the Linux64 binaries.

You might try the 32bit version for Linux. It takes less than 2 minutes
with a decent internet connection. After pasting the whole thing you
only have to wait the result:

cd && mkdir temp-ctx-install && cd temp-ctx-install &&\
rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh . &&\
./first-setup.sh --platform=linux --modules=all && cd &&\
source temp-ctx-install/tex/setuptex && mtxrunjit --generate\
&& echo "\starttext a\footnote{b}\stoptext" \
> test-ctx-temp.mkiv && contextjit --purgeall test-ctx-temp.mkiv

If that works, you may copy from my previous message to test again.

Don’t get me wrong. I think this is the best way of testing it, since
I’m not in front of your computer. And I don’t have a 64bit computer to
test, either.

Just in case it helps,

Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2017-02-16 21:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 18:51 j. van den hoff
2017-02-16 19:32 ` Alan Braslau
2017-02-16 19:36   ` j. van den hoff
2017-02-16 20:04     ` Marcus Vinicius Mesquita
2017-02-16 20:40 ` Pablo Rodriguez
2017-02-16 20:54   ` Alan Braslau
2017-02-16 20:56     ` j. van den hoff
2017-02-16 21:20       ` Pablo Rodriguez [this message]
2017-02-16 21:32         ` j. van den hoff
2017-02-16 21:51           ` Pablo Rodriguez
2017-02-16 22:02       ` Alan Braslau
2017-02-17  9:13 ` Hans Hagen
2017-02-17  9:28   ` Hans Hagen
2017-02-17 10:13     ` strange crash -- SOLVED j. van den hoff
2017-02-17 10:45     ` strange crash Peter Rolf
2017-02-17 13:30       ` luigi scarso
2017-02-17 13:41         ` Peter Rolf
2017-02-18  9:32     ` Lutz Haseloff
2017-02-18  9:50       ` luigi scarso
2017-02-18 10:00         ` Lutz Haseloff
2017-02-18 10:45           ` luigi scarso
2017-02-18 10:59             ` Lutz Haseloff
2017-02-18 11:06               ` luigi scarso
2017-02-18 11:49                 ` Lutz Haseloff
2017-02-18 11:55                   ` luigi scarso
2017-02-18 13:11                     ` Lutz Haseloff
2017-02-18 12:15                   ` luigi scarso

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=e8f8f0cf-f359-ae92-1485-162f5277db39@gmx.es \
    --to=oinos@gmx.es \
    --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).