ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans van der Meer <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: mpost finds BAD TFM
Date: Mon, 22 Dec 2008 19:08:54 +0100	[thread overview]
Message-ID: <1924EAF8-FAF8-4B6F-95EB-9F187711EF36@uva.nl> (raw)

NASTY PROBLEM WITH READING TFM FILES IN LATEST METAPOST

A nasty problem has surfaced that Taco Hoekwater cannot solve, because  
it does not occur on his system. My system is Apple Macintosh 10.5.6  
and I am using the command "sh build.sh" to compile metapost-1.101.

After compiling and generating with "mpost --ini mpost" the error  
message below result when calling "make" in the manual-directory of  
the distribution. It signals a bad tfm file, I guess because the wrong  
number of bytes is read. Some 16/32/64 bit issue perhaps? Taco has not  
found it and as his compile now runs "lint-free" it is difficult to  
imagine what can be wrong.
Are there people in this group (preferably on Macintosh) who find the  
same thing happening? And then are far more apt with debuggers than I  
am?

Many thanks in advance.
Hans van der Meer


This says the logfile of the mpost run, the programcode involved is  
from source file tfmin.w:

This is MetaPost, version 1.101 (kpathsea version 3.5.7) (mem=mpost  
2008.12.22)  22 DEC 2008 17:53
**mpman
(/usr/local/texlive/2008/texmf-dist/metapost/base/boxes.mp)
! Font cmr10 not usable: TFM file is bad.
_s->...oup.addto._p.also(EXPR2)infont(EXPR3)scaled
                                                   
(EXPR4)shifted((EXPR5),(EX...
<argument> ..._n0="cmr10";_s("Figures",_n0,1,0,0,)
                                                  ;_s 
("in",_n0,1,35.3674,0,)...

beginbox_->...UFFIX2):=nullpicture;for._p_=(TEXT3)
                                                  :pic_ 
(SUFFIX2):=if.picture...

boxit->..."boxpath_","sizebox_",(SUFFIX2),(TEXT3))
                                                  ;generic_declare 
(pair)_n.s...
l.26 ....aa(btex \place{Figures in MetaPost} etex)
                                                  ;


___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


             reply	other threads:[~2008-12-22 18:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22 18:08 Hans van der Meer [this message]
2008-12-22 19:52 ` Aditya Mahajan
2008-12-22 20:52   ` Hans van der Meer
2008-12-22 21:20   ` Taco Hoekwater
2008-12-22 21:51 ` luigi scarso
2008-12-23  0:13 ` Mojca Miklavec
2008-12-23 16:27 ` Fixed: " Taco Hoekwater

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=1924EAF8-FAF8-4B6F-95EB-9F187711EF36@uva.nl \
    --to=h.vandermeer@uva.nl \
    --cc=ntg-context@ntg.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).