From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/4454 Path: main.gmane.org!not-for-mail From: guravage@nlr.nl Newsgroups: gmane.comp.tex.context Subject: metafun configuration problem? Date: Fri, 23 Mar 2001 12:03:57 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <200103231103.MAA03836@thucydides.nlr.nl> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035395120 25882 80.91.224.250 (23 Oct 2002 17:45:20 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:45:20 +0000 (UTC) Original-To: ntg-context@ntg.nl Xref: main.gmane.org gmane.comp.tex.context:4454 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:4454 I am having problems running the self same context file on two similar TeX installations. I would greatly appreciate if anyone could offer any advice how I can track down and resolve the discrepancy. First, here's a simple test file that exemplifies the problem: % interface=en output=pdftex \starttext \startMPpage draw btex foo etex \stopMPpage \stoptext System A has tex-live-5 installed, and the latest version of context replacing that of the distribution. When I run `texexec life_cycle' the log shows just what you'd expect: systems : begin file foo at line 2 \openout1 = `foo-mpgraph.mp'. Randomizer initialized to 807553133. system(texexec --batch --output=dvips --mpformat=metafun --mptex --nomp --once foo-mpgraph)...executed. [MP to PDF foo-mpgraph.1] (./foo-mpgraph.1) layout : calculating backgrounds System B has tex-live-5 installed, and the latest context installed in a separate texmf tree. The log of the same command run on B gives the first indication of a problem: \openout1 = `foo-mpgraph.mp'. Randomizer initialized to 794719257. system(texexec --batch --output=dvips --mpformat=metafun --mptex --nomp --once foo-mpgraph)...executed. figures : figure foo-mpgraph can not be found layout : calculating backgrounds So I ran the batch command explicitly on system A and all appears fine: TeXExec 2.5 - ConTeXt / PRAGMA ADE 1997-2001 metapost to tex : foo-mpgraph executable : pdfetex format : cont-en inputfile : tmpgraph output : dvips interface : en options : once batch nomp current mode : all This is pdfeTeX, Version 3.14159-14f-released-20000525-2.1 (Web2C 7.3.2x) entering extended mode run time : 1 seconds dvi to metapost : foo-mpgraph metapost : foo-mpgraph format : metafun This is MetaPost, Version 0.641 (Web2C 7.3.2x) Running the same command on system B dies prematurely with the error, "sh: mptotex command not found." TeXExec 2.5 - ConTeXt / PRAGMA ADE 1997-2001 metapost to tex : foo-mpgraph sh: mptotex: command not found metapost : foo-mpgraph format : metafun This is MetaPost, Version 0.641 (Web2C 7.3.2x) The generated foo-mpgraph.mp files from both systems are identical with the exception of the ramdomseed assignment on line 3. Running metapost directly with the foo-mpgraph.mp on system A yields: mpost foo-mpgraph.mp This is MetaPost, Version 0.641 (Web2C 7.3.2x) (foo-mpgraph.mp (/shared/home/nlr/isens/share/TeXLive5d/texmf/metapost/context/mp-tool.mp) (/shared/home/nlr/isens/share/TeXLive5d/texmf/metapost/context/mp-spec.mp) (/shared/home/nlr/isens/share/TeXLive5d/texmf/metapost/context/mp-grph.mp) (/shared/home/nlr/isens/share/TeXLive5d/texmf/metapost/context/mp-page.mp) (/shared/home/nlr/isens/share/TeXLive5d/texmf/metapost/context/mp-core.mp) [1] ) 1 output file written: foo-mpgraph.1 Transcript written on foo-mpgraph.log. Running the same command on system B yields: mpost foo-mpgraph.mp This is MetaPost, Version 0.641 (Web2C 7.3.2x) (foo-mpgraph.mp (/home/michael/texmf/metapost/context/mp-tool.mp) (/home/michael/texmf/metapost/context/mp-spec.mp) (/home/michael/texmf/metapost/context/mp-grph.mp) (/home/michael/texmf/metapost/context/mp-page.mp) (/home/michael/texmf/metapost/context/mp-core.mp)/opt/TeX/bin/i386-linux/makemp x: Command failed: tex mpxerr.tex; see mpxerr.log >> foo-mpgraph.mp >> foo-mpgraph.mpx ! Unable to make mpx file. l.83 draw btex foo etex Transcript written on foo-mpgraph.log. The contents of mpxerr.tex are: \global \loadfontdefinitionfileoncetrue% \shipout\hbox{\smash{\hbox{\hbox{% line 83 foo-mpgraph.mp foo}\vrule width1sp}}} \end{document} And the contents of mpxerr.log are: This is TeX, Version 3.14159 (Web2C 7.3.2x) (format=tex 2000.9.5) 23 MAR 2001 11:55 **mpx3730.tex (./mpx3730.tex ! Undefined control sequence. l.1 \global \loadfontdefinitionfileoncetrue % The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., `\hobx'), type `I' and the correct spelling (e.g., `I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. ! You can't use a prefix with `\shipout'. \shipout l.2 \shipout \hbox{\smash{\hbox{\hbox{% line 83 foo-mpgraph.mp I'll pretend you didn't say \long or \outer or \global. [1] ) Output written on mpx3730.dvi (1 page, 196 bytes). I've compared the texmf.cnf and cont-sys.tex files from both systems, but I don't any significant differences. Both systems use the self same TeX and the latest context distributions - except that system B has a later version of pdftex, and system B has context and pdftex in a separate texmf tree. As I said, I would appreciate any suggestions how I might track down and resolve this discrepancy. Cheers, Michael -- Michael A. Guravage Email: guravage@nlr.nl National Aerospace Laboratory Phone: +31 (0)20 511 3695 P.O. Box 90502, 1006 BM, Fax: +31 (0)20 511 3210 Amsterdam, The Netherlands URL: