From: "Uwe Koloska" <uwe.koloska@mailbox.tu-dresden.de>
Subject: Re: metapost not invoked? mpgraph.1 not created
Date: Wed, 21 Feb 2001 03:08:16 +0100 [thread overview]
Message-ID: <01022103081602.25740@bilbo> (raw)
In-Reply-To: <200102201048.LAA25097@sol.cs.uni-dortmund.de>
You wrote on Dienstag, 20. Februar 2001 11:48:
>Hi Hans and others,
>
>> >mprun.log:systems : please update your pdfTeX binaries
>>
>> eh, maybe, how old is your pdftex? On our site there are pointers to
>> newer binaries (thanh has a linux one on his site).
>
>i've just compiled a new binary -> same problem.
How did you install your TeX system? I suppose you use tetex. Then if you
install a new version of pdftex, you have to make sure that all paths are
set correctly -- I don't know wether other versions use the same
configuration than tetex ...
Normally by installing tetex, the location of the texmf-tree is compiled in
and so the programs can found the configuration (texmf.cnf) without setting
any environment variable. Make sure, that your new pdftex uses the same
configuration by setting TEXMF or similar (look at the docs).
If you are not so familar with unix (for debugging purposes) I suggest you
install a up to date version of tetex (the beta from 18.12.2000 works ok
here and has a new enough pdftex
pdfTeX, Version 3.14159-14f-released-20000525 (Web2C 7.3.1)
So if you have no solution, examine your system and describe what you have
done to install (te)tex, pdftex and context.
Yours
Uwe
--
mailto:koloska@rcs.urz.tu-dresden.de
http://rcswww.urz.tu-dresden.de/~koloska/
-- --
right now the web page is in german only
but this will change as time goes by ;-)
next prev parent reply other threads:[~2001-02-21 2:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Your message of "Mon, 19 Feb 2001 17:22:59 +0100." <3.0.6.32.20010219172259.0157a600@server-1>
2001-02-20 10:48 ` Patrick Gundlach
2001-02-20 11:53 ` Hans Hagen
2001-02-20 15:42 ` Ed L Cashin
2001-02-20 15:58 ` Marc van Dongen
2001-02-20 16:40 ` Hans Hagen
2001-03-15 11:10 ` Slawek Zak
2001-03-15 11:14 ` Slawek Zak
2001-03-15 12:41 ` Patrick Gundlach
2001-03-15 19:45 ` Ed L Cashin
2001-02-20 21:22 ` Ed L Cashin
2001-02-21 12:51 ` Marc van Dongen
2001-02-21 16:53 ` Ed L Cashin
2001-02-21 17:17 ` Marc van Dongen
2001-02-21 17:22 ` Marc van Dongen
2001-02-21 2:08 ` Uwe Koloska [this message]
2001-02-22 15:55 Patrick Gundlach
-- strict thread matches above, loose matches on Subject: below --
2001-02-22 15:39 Patrick Gundlach
[not found] <Your message of "Tue, 20 Feb 2001 12:53:44 +0100." <3.0.6.32.20010220125344.01cc87b0@server-1>
2001-02-20 14:16 ` Patrick Gundlach
2001-02-20 16:46 ` Hans Hagen
2001-02-20 21:35 ` Ed L Cashin
2001-02-20 14:13 Patrick Gundlach
[not found] <Your message of "Mon, 19 Feb 2001 15:59:52 +0100." <3.0.6.32.20010219155952.019f7180@server-1>
2001-02-19 15:47 ` Patrick Gundlach
2001-02-19 16:22 ` Hans Hagen
[not found] <Your message of "Mon, 19 Feb 2001 11:47:49 +0100." <3.0.6.32.20010219114749.017fb4d0@server-1>
2001-02-19 12:57 ` Patrick Gundlach
2001-02-19 14:59 ` Hans Hagen
2001-02-21 2:16 ` Uwe Koloska
2001-02-17 15:24 Patrick Gundlach
2001-02-19 10:47 ` Hans Hagen
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=01022103081602.25740@bilbo \
--to=uwe.koloska@mailbox.tu-dresden.de \
/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).