Re: Re: first attempt to run mp (system error)

["Paweł Jackowski (onet)" <jackos1@poczta.onet.pl>]

Problem: system error while running texexec --automprun

07-10-2003, 18:02, Patrick Gundlach: 
> Hi,
> 
> I am not a windows user, but what happens if you run mpost.exe on the
> mpgraph.mp file? Do you get the same error?

Yes, indeed! But compiling code

	beginfig(100)
	 fill unitsquare scaled 123 withcolor (.2,.3,.4);
	endfig;
	end

doesn't causes any errors, which means that so mpost program works ok.
The problem is in the mpgraph.mp. I use the same texmf tree for linux
and windows, so I can compare how it works with linux binaries. En error
also occur in linux:

	This is MetaPost, Version 0.641 (Web2C 7.3.7x)
	(mpgraph.mp (/mnt/winXP/TeX/texmf/metapost/context/mp-tool.mp)
	(/mnt/winXP/TeX/texmf/metapost/context/mp-spec.mp)
	(/mnt/winXP/TeX/texmf/metapost/context/mp-grph.mp)
	(/mnt/winXP/TeX/texmf/metapost/context/mp-page.mp)
	(/mnt/winXP/TeX/texmf/metapost/context/mp-core.mp)Naruszenie 	ochrony
pamięci


The last alert means "Memory violating". A remedy for such problems is
to regenerate the format. However the wrong metafun format was generated
with fmtutil and its default settings... Anyway I have regenerated
metafun format with command:

	texexec --make --alone metafun


But unfortunately regenerating format is not the whole story.
After that I tried to compile under windows following code:

	\starttext
		The simplest metapost code
	\startMPgraphic
		fill unitsquare scaled 123 withcolor (.2,.3,.4);
	\stopMPgraphic
	\stoptext

(Is there something wrong in it?)
After running 'texexec --automprun --pdf sample.tex' MetaPost generated
nice mpgraph.1. I also tried 'mpost mpgraph.mp' which doesn't cause
problems any more. The only problem is that PDF output didn't contain
the graphic!

Under linux the problem is even stranger. Running 'texexec --automprun
--pdf sample.tex' produce (as in windows) proper postscript code
mpgraph.1 (properly interpreted and displayed by ghostscript). But
running 'mpost mpgraph.mp' under linux still causes the "Memory
violating" error. PDF output also doesn't contain the graphic.

Unfortunately mpgraph.log is empty (zero length file) and tex log file
doesn't inform about any problems.

I'm afraid there are at least two independent problems: no graphic in
PDF output and "Memory violating" error (regenerating format can't help
here).


:-?


Thanks, Paawe/l