ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: guravage@nlr.nl
Subject: metafun configuration problem?
Date: Fri, 23 Mar 2001 12:03:57 +0100	[thread overview]
Message-ID: <200103231103.MAA03836@thucydides.nlr.nl> (raw)

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'.
<to be read again> 
                   \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:   <http://www.nlr.nl>


             reply	other threads:[~2001-03-23 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-23 11:03 guravage [this message]
2001-03-23 11:33 ` Hans Hagen
2001-03-23 11:35 ` Hans Hagen
2001-03-23 15:32 guravage

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=200103231103.MAA03836@thucydides.nlr.nl \
    --to=guravage@nlr.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).