From: "luigi scarso" <luigi.scarso@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: mpost finds BAD TFM
Date: Mon, 22 Dec 2008 22:51:04 +0100 [thread overview]
Message-ID: <fe8d59da0812221351l31331a1ua8adc9afe1a52e6e@mail.gmail.com> (raw)
In-Reply-To: <1924EAF8-FAF8-4B6F-95EB-9F187711EF36@uva.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1568 bytes --]
On Mon, Dec 22, 2008 at 7:08 PM, Hans van der Meer <H.vanderMeer@uva.nl>wrote:
> 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
>
I'm not able to reproduce this problem in my linux box with texlive 2008
Here is my steps
1) downloaded metapost-1.101-src.tar.bz2 and compiled with ./build.sh :
OK
2) copied mpost to texlive2008 standard bin directory,
(in my case texlive/2008/bin/i386-linux)
activated texlive2008
(cd texlive/2008; . setuptex ;)
remade all format
fmtutil --all; mktexlsr
OK
3) cd metapost-1.101/manual-test; make
OK
7,3K 2008-12-22 22:38 grdemo-doc.pdf
3,0K 2008-12-22 22:38 grdemo.pdf
363K 2008-12-22 22:38 mpboxes.pdf
457K 2008-12-22 22:38 mpgraph.pdf
193K 2008-12-22 22:38 mpintro.pdf
760K 2008-12-22 22:38 mpman.pdf
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 2020 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-12-22 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 18:08 Hans van der Meer
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 [this message]
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=fe8d59da0812221351l31331a1ua8adc9afe1a52e6e@mail.gmail.com \
--to=luigi.scarso@gmail.com \
--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).