From: Patrick Gundlach <pg@levana.de>
Subject: Re: MetaPost error
Date: Thu, 04 Sep 2003 18:43:51 +0200 [thread overview]
Message-ID: <m27k4ocxmg.fsf@levana.de> (raw)
In-Reply-To: <e088e187.e187e088@poczta.teleton.pl> (nitram@emil.teleton.pl's message of "Thu, 04 Sep 2003 13:32:53 +0200")
"^Nitram^" <nitram@emil.teleton.pl> writes:
Hi,
> I generate: makemem metafun
> I did texexec --make --alone metafun
OK, this is the way to go.
> and I still have error:
>
> initexmf: don't know to dump metafun
> I can't find default mem file!
this is odd. What is this initexmf?
After texexec --make --alone metafun the metafun.mem file needs to be placed in teh appropriate directory (web2c on web2c systems. Don't know about Miktex)
Some more information would be useful:
do ConTeXt files (without metapost stuff) work correctly?
what system are you using?
what is the version of your ConTeXt system?
And please post the exact steps you did and the exact error messages.
Patrick
next prev parent reply other threads:[~2003-09-04 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 11:32 ^Nitram^
2003-09-04 16:43 ` Patrick Gundlach [this message]
2003-09-04 19:30 ` Willi Egger
2003-09-05 5:24 ^Nitram^
2011-10-19 11:34 Metapost error Lutz Haseloff
2011-10-19 15:16 ` luigi scarso
2011-10-20 4:28 ` Lutz Haseloff
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=m27k4ocxmg.fsf@levana.de \
--to=pg@levana.de \
--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).