MetaPost problem / workaround

Thursday, 21 July 2005 21:17 by CSchenk

Due to some altered memory settings in miktex.ini, it is required to refresh the dump files (*.fmt;*.efmt;*.base;*.mem). Normally this happens automatically. But this time MetaPost fails to "recognize" the new memory settings and stops with an error message ("I'm broken. Please show this to someone who can fix can fix"). The workaround is simple: creating new dump files (via MiKTeX Options) solves the problem. For more information, see this bug report.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5
Tags:  
Categories:   MiKTeX Packaging
Actions:   E-mail | Permalink | Comments (4) | Comment RSSRSS comment feed

Related posts

Comments

August 10. 2005 11:45

Risto Kuusisto

I also have the same problem and I did as you explained (i.e. refreshing). Still the same problem. Here's the log-file when using the metapost example file figs.mp:
===
This is MetaPost, Version 0.901 (MiKTeX 2.4) (preloaded mem=plain 2005.8.10) 10 AUG 2005 19:38
**figs
(figs.mp (boxes.mp)
>> figs.mp
>> figs.mpx
! Unable to make mpx file.
l.16 boxit.a(btex
\s8A\s+2 \(lh a etex);
The two files given above are one of your source files
and an auxiliary file I need to read to find out what your
btex..etex blocks mean. If you don't know why I had trouble,
try running it manually through MPtoTeX, TeX, and DVItoMP
===
ristojk@tuubi.net





Risto Kuusisto

August 11. 2005 00:35

I think this problem is unrelated to the "I'm broken" problem. A DebugView trace should give us some information. You should start mpost as follows:

mp --trace=config,error,process figs.mp

You can send the log file to bugs @ miktex.org.

Christian Schenk

November 13. 2005 17:49

Haldun

Has the issue first reported by Kuusisto on 10 August been addressed? I have been experiencing exactly the same problem.

Haldun

Haldun

July 14. 2009 04:14

pingback

Pingback from answerspluto.com

list of urls - 5 « Answers Pluto

answerspluto.com

Comments are closed