[metapost] metapost-1.503 format files

[Reinhard Kotucha]

On 16 November 2010 Karel wrote:

 > Reinhard Kotucha napsal(a):
 > > Hi,
 > > when I run
 > > 
 > >   mpost -ini  -jobname=mpost -progname=mpost mpost.mp
 > > 
 > > with metapost 1.503 from tlcontrib on x86_64-linux I get
 > > 
 > > ----------------------------------------------------------
 > > This is MetaPost, version 1.503 (kpathsea version 6.0.0)
 > > (/usr/local/texlive/2010/texmf-dist/metapost/base/mpost.mp
 > > (/usr/local/texlive/2010/texmf-dist/metapost/base/plain.mp
 > > Preloading the plain mem file, version 1.004) )
 > > Transcript written on mpost.log.
 > > ----------------------------------------------------------
 > > 
 > > The log file contains the same except the last line.  It seems that
 > > metapost 1.503 doesn't execute the dump command.
 > > 
 > > When I replace the binary by that one from the TL repository (v 1.211)
 > > a .mem file is created.
 > > 
 > > ----------------------------------------------------------
 > > This is MetaPost, version 1.211 (TeX Live 2010) (kpathsea version 6.0.0) (INIMP)
 > > (/usr/local/texlive/2010/texmf-dist/metapost/base/mpost.mp
 > > (/usr/local/texlive/2010/texmf-dist/metapost/base/plain.mp
 > > Preloading the plain mem file, version 1.004) )
 > > Beginning to dump on file mpost.mem
 > >  (mem=mpost 2010.11.16)
 > > at most 745 strings of total length 3693
 > > 3412 memory locations dumped; current usage is 1036&2302
 > > 507 symbolic tokens
 > > Transcript written on mpost.log.
 > > ----------------------------------------------------------
 > > 
 > > Can anybody reproduce the problem?  I'm quite clueless and wondering 
 > > why I didn't encounter the problem earlier.  To make sure that the
 > > correct binary is used, I downloaded metapost.x86_64-linux.tar from
 > > tlcontrib and replaced the binary, but I still don't get a .mem file.
 > > 
 > > Regards,
 > >   Reinhard
 > > 
 > 
 > It was announced several times that some future versions of 
 > metapost (mplib) woun't produce mem file any more, when using with 
 > some -mem oprion should result in reading th corresponding mp file.
 > 
 > Taco will probably explain this behaviour better:-)

Hi Karel,
thanks for the hint.  It's fine if no mem files are needed anymore.

I stumbled about it because there was still an entry in updmap.cfg 
and updmap complains loudly if it can't create a mem file.

Thanks,
  Reinhard

-- 
----------------------------------------------------------------------------
Reinhard Kotucha			              Phone: +49-511-3373112
Marschnerstr. 25
D-30167 Hannover	                      mailto:reinhard.kotucha at web.de
----------------------------------------------------------------------------
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
----------------------------------------------------------------------------