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!