ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Patrick Gundlach <pg@levana.de>
Subject: Re: first attempt to run mp (system error) -- summary?
Date: Wed, 08 Oct 2003 23:22:02 +0200	[thread overview]
Message-ID: <m2llrvpgqt.fsf@levana.de> (raw)
In-Reply-To: <006f01c38dd9$92077dd0$0500a8c0@best> (Pawel Jackowski na Onet's message of "Wed, 8 Oct 2003 22:19:43 +0200")

Hi,

> Pawe/l wrote about:
> 1. System error while compiling nested mp code (under Windows) --
> regenerating metafun format solves that

good to hear.

> 2. 'Memory violating' error while compiling nested mp code (under Linux) --
> still can't find the answer...

that is really strange. If you are brave and experienced, you might
trace the mpost run with strace to see where the error occurs. 

Please post the logfile of the bad run.

> 3. Missed mp graphics in output PDF -- solved of course... sorry for that
> silly question, I've taken the first example appearing in ConTeXt manual
> assuming that it is the basic one.

This question was not silly at all. I am still confused by the
plethora of ways to run mp.

>> you don't need --automprun. Everything should work fine w/o.
>
> I tried to omit this option, but without that MetaPost doesn't run at all.

could you post the output of texexec --verbose and the logfile of a
simple ConTeXt file with mp code in it?

> Doesn't hurt. ...But wait -- I aks to be on the safe side: since I remember,
> I use common formats (and every other files in texmf tree) for linux and
> windows. Is there ANY reason to generate nativ format for each operating
> system? Is there any reason not to make common any other texmf
> files?

I'd like to know, too.

> Surely I will! Which version has tl2003 binarises: linux, windows or both?
> By the way, does anybody know if tl2003 binaries are frozen already?

<url:http://www.tug.org/texlive/>

For TeX Live 2003, the last update of packages and programs was made
on 20 September 2003.  For the latest versions, please consult CTAN .

Patrick
-- 
You are your own rainbow!

  reply	other threads:[~2003-10-08 21:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07  7:42 first attempt to run mp Pawel Jackowski na Onet
2003-10-07  8:08 ` Willi Egger
2003-10-07 14:31   ` first attempt to run mp (system error) Pawel Jackowski na Onet
2003-10-07 15:40     ` Willi Egger
2003-10-07 16:02 ` first attempt to run mp Patrick Gundlach
2003-10-08  7:27   ` Re: first attempt to run mp (system error) Paweł Jackowski (onet)
2003-10-08  7:53     ` Hans Hagen
2003-10-08 20:19       ` first attempt to run mp (system error) -- summary? Pawel Jackowski na Onet
2003-10-08 21:22         ` Patrick Gundlach [this message]
2003-10-09  6:50           ` Pawel Jackowski na Onet
2003-10-08 21:41         ` Patrick Gundlach
2003-10-08 22:16           ` Hans Hagen
2003-10-09  8:38         ` Henning Hraban Ramm
2003-10-08  8:04     ` Re: first attempt to run mp (system error) Willi Egger
2003-10-08 16:32     ` Patrick Gundlach

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=m2llrvpgqt.fsf@levana.de \
    --to=pg@levana.de \
    --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).