From: Willi Egger <w.egger@boede.nl>
Subject: Re: Re: first attempt to run mp (system error)
Date: Wed, 08 Oct 2003 10:04:23 +0200 [thread overview]
Message-ID: <6.0.0.22.1.20031008095252.01ba3eb8@digitpaint.nl> (raw)
In-Reply-To: <1065598042.4594.36.camel@PawCooLinux>
At 09:27 08.10.2003, Pawel wrote:
>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!
Shure, the graphic was not called to be placed in the document!
So you might add \useMPgraphic
This works here:
\setupoutput[pdftex]
\setupcolors[state=start]
\starttext
The simplest metapost code
\startuseMPgraphic{test}
fill unitsquare scaled 123 withcolor (.2,.3,.4);
\stopuseMPgraphic
\useMPgraphic{test}
\stoptext
Willi
>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
>
>
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2003-10-08 8:04 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
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 ` Willi Egger [this message]
2003-10-08 16:32 ` first attempt to run mp (system error) 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=6.0.0.22.1.20031008095252.01ba3eb8@digitpaint.nl \
--to=w.egger@boede.nl \
--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).