From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/13763 Path: main.gmane.org!not-for-mail From: Willi Egger Newsgroups: gmane.comp.tex.context Subject: Re: Re: first attempt to run mp (system error) Date: Wed, 08 Oct 2003 10:04:23 +0200 Sender: ntg-context-admin@ntg.nl Message-ID: <6.0.0.22.1.20031008095252.01ba3eb8@digitpaint.nl> References: <000901c38ca6$8af7a0d0$0500a8c0@best> <1065598042.4594.36.camel@PawCooLinux> Reply-To: ntg-context@ntg.nl NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1065600704 12400 80.91.224.253 (8 Oct 2003 08:11:44 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 8 Oct 2003 08:11:44 +0000 (UTC) Original-X-From: ntg-context-admin@ntg.nl Wed Oct 08 10:11:43 2003 Return-path: Original-Received: from ref.vet.uu.nl ([131.211.172.13] helo=ref.ntg.nl) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1A79Q6-0005Vh-00 for ; Wed, 08 Oct 2003 10:11:43 +0200 Original-Received: from ref.ntg.nl (localhost.localdomain [127.0.0.1]) by ref.ntg.nl (Postfix) with ESMTP id CD0DA10B57; Wed, 8 Oct 2003 10:11:40 +0200 (MEST) Original-Received: from smtpzilla3.xs4all.nl (smtpzilla3.xs4all.nl [194.109.127.139]) by ref.ntg.nl (Postfix) with ESMTP id A91EF10B0E for ; Wed, 8 Oct 2003 10:04:22 +0200 (MEST) Original-Received: from vademecum.boede.nl (a80-126-172-1.adsl.xs4all.nl [80.126.172.1]) by smtpzilla3.xs4all.nl (8.12.9/8.12.9) with ESMTP id h9884JfX072589 for ; Wed, 8 Oct 2003 10:04:20 +0200 (CEST) X-Sender: boedenl01@digitpaint.nl X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Original-To: ntg-context@ntg.nl In-Reply-To: <1065598042.4594.36.camel@PawCooLinux> Original-References: <000901c38ca6$8af7a0d0$0500a8c0@best> <1065598042.4594.36.camel@PawCooLinux> Errors-To: ntg-context-admin@ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.comp.tex.context:13763 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:13763 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=20 > ochrony >pami=EAci > > >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=3Dstart] \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