From: Axel Zindler <a.zindler@gmx.de>
Subject: Re: fmtutil can't find pdfetex.pool
Date: Thu, 22 Nov 2001 13:28:27 +0100 (MET) [thread overview]
Message-ID: <6818.1006432107@www2.gmx.net> (raw)
Hi all,
sorry, that I have bothered you with this.
I've found the solution yesterday myself after reading the write manual ;-)
--> pdftexman.pdf
The problem comes with the binary version of pdftex. These files have
incompiled possible search paths for the file texmf.cnf. In SuSE 7.3 it
resides in /var/lib/texmf/web2c and this path is not the search path
compiled
inside the binaries.
With
pdftex -kpathsea-debug=255 -ini -fmt=cont-en cont-en
one can find the problems a little bit more in detail.
Then one can create a link with
su - root
cd /usr/share/texmf/teTeX/bin/i386-linux-glibc
ln -s /var/lib/texmf/web2c/texmf.cnf texmf.cnf
to the relevant file.
and
/usr/share/texmf/texexec --make
works perfect
Greetings
Axel Zindler
Anyway Thanks Christoph.
Am Montag, 19. November 2001 21:30 schrieben Sie:
> Hi all,
>
> after downloading the file pdftex-linux-20010417.zip from the ftp-archiv I
> wanted to make the new formats.
> Instead I'm getting:
>
> axel@asus:~> texexec --make
>
> TeXExec 2.6 - ConTeXt / PRAGMA ADE 1997-2001
>
> ! I can't read pdfetex.pool; bad path?
> fmtutil: `pdfetex -ini -efmt=cont-en -progname=context *cont-en.ini'
> failed. ! I can't read pdfetex.pool; bad path?
> fmtutil: `pdfetex -ini -efmt=cont-nl -progname=context *cont-nl.ini'
> failed. This is MetaPost, Version 0.641 (Web2C 7.3.1) (INIMP)
> (/usr/share/texmf/metapost/context/metafun.mp
> (/usr/share/texmf/metapost/base/plain.mp
> Preloading the plain mem file, version 0.63)
> (/usr/share/texmf/metapost/context/mp-tool.mp)
> (/usr/share/texmf/metapost/context/mp-spec.mp)
> (/usr/share/texmf/metapost/context/mp-core.mp)
> (/usr/share/texmf/metapost/context/mp-page.mp)
> (/usr/share/texmf/metapost/context/mp-text.mp)
> (/usr/share/texmf/metapost/context/mp-shap.mp)
> (/usr/share/texmf/metapost/context/mp-butt.mp)
> (/usr/share/texmf/metapost/context/mp-char.mp)
> (/usr/share/texmf/metapost/context/mp-step.mp)
> (/usr/share/texmf/metapost/context/mp-grph.mp) )
> Beginning to dump on file metafun.mem
> (mem=metafun 2001.11.19)
> at most 2354 strings of total length 32081
> 32532 memory locations dumped; current usage is 10024&22419
> 1290 symbolic tokens
> Transcript written on metafun.log.
> ! I can't read pdfetex.pool; bad path?
>
> TeX binary : pdfetex
> format(s) : en nl metafun mptopdf
>
>
> total run time : 4 seconds
> axel@asus:~> kpsewhich pdfetex.pool
> /var/lib/texmf/web2c/pdfetex.pool
>
> the files pdftex.pool and pdfetex.pool had been updated.
>
> Any hints how I can find what's wrong??
>
> Thanks
>
> Axel Zindler
--
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
next reply other threads:[~2001-11-22 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 12:28 Axel Zindler [this message]
2001-11-23 16:06 ` Christopher Creutzig
-- strict thread matches above, loose matches on Subject: below --
2001-11-24 16:56 Axel Zindler
2001-11-23 19:02 Axel Zindler
2001-11-23 19:39 ` George N. White III
2001-11-19 18:06 Axel Zindler
2001-11-21 15:10 ` Christopher Creutzig
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=6818.1006432107@www2.gmx.net \
--to=a.zindler@gmx.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).