ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: flip phillips <flip@skidmore.edu>
Subject: More: metapost crashing w/ current teTeX
Date: Mon, 8 Apr 2002 00:35:39 -0400	[thread overview]
Message-ID: <13DDD0B7-4AAA-11D6-88D4-0003931DE38A@skidmore.edu> (raw)

So, stupid me, in the example presented I forgot to do -mem=metafun...
When I do so, the mpgraph.mp file compiles fine, creating the graphics 
in question in the local directory.

However, when run from a contex session (using TeXShop, btw) I get an 
address violation in mpost. (I can tell since the Console.app pops up a 
window w/ said backtrace). The mpgaph.log is empty, presumably since 
mpost never got its gears meshed.

Strange and yet, true!

I'm sort of at the end of my personal rope here on this one... looked at 
all the configurations and temp locations, etc. that I know of, so I'm 
confused...

Begin forwarded message:

> I've recently installed, via the new i-installer mechanism, teTeX, 
> ghostscript.
--
flip phillips
http://www.skidmore.edu/~flip/


                 reply	other threads:[~2002-04-08  4:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=13DDD0B7-4AAA-11D6-88D4-0003931DE38A@skidmore.edu \
    --to=flip@skidmore.edu \
    /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).