From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: Problem with ConTeXt installation
Date: Sat, 30 Sep 2006 22:02:04 +0100 [thread overview]
Message-ID: <E1GTlyG-0001Im-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Sat, 30 Sep 2006 16:21:08 EDT." <200609301621.09146.jazz_johnson@verizon.net>
> So I simply copied /root/.texmf-var/web2c/pdfetex/* /var/lib/texmf/web2c/
> "texexec new.tex" seems to run OK now, without error.
> I'll investigate further.
You run texexec as root, I'm guessing, so that the formats will be
visible to all users. However, that means they go into root's
.texmf-var/ directory because the TEXFORMATS kpse variable contains
the home-directory .texmf-var before /var/lib/texmf. Here's how to
check:
$ kpsewhich --expand-path='$TEXFORMATS'
.:/home/sanjoy/.texmf-var/web2c:/home/sanjoy/texmf/web2c:/var/lib/texmf/web2c:/usr/local/share/texmf/web2c:/usr/share/texmf/web2c:/usr/share/texmf-tetex/web2c
Yup, ~/.texmf-var/web2c comes first.
That's due to these lines in /etc/texmf/texmf.cnf, at least on my
Ubuntu (teTeX 3.0) system:
TEXMF = {$TEXMFCONFIG,$TEXMFVAR,$TEXMFHOME,$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFLOCAL,!!$TEXMFMAIN,!!$TEXMFDIST}
TEXFORMATS = .;$TEXMF/web2c/{$engine,}
The TEXMFVAR is short for $HOME/.texmf-var and is what means the
formats go in /root/.texmf-var/. So, you need to change TEXFORMATS
for the texexec run, telling it to place them in /var/lib/texmf:
# TEXFORMATS='/var/lib/texmf/web2c/{$engine,}' texexec --make --all
Or slightly more general, in case TEXMFSYSVAR changes someday from
/var/lib/texmf (note all the horrid quoting):
# TEXFORMATS=`kpsewhich --expand-path='$TEXMFSYSVAR'`'/web2c/{$engine,}' \
texexec --make --all
I just tried it as root, and it seemed to work -- I got brand-new
formats in /var/lib/texmf/web2c/pdfetex:
# ls /var/lib/texmf/web2c/pdfetex/*.fmt
/var/lib/texmf/web2c/pdfetex/cont-nl.fmt
/var/lib/texmf/web2c/pdfetex/mptopdf.fmt
/var/lib/texmf/web2c/pdfetex/cont-en.fmt
> # for f in `kpsewhere -engine=pdfetex cont-en.fmt`; do ls -l ${f}; done
Or slightly simpler (using -U to preserve the order produced by
kpsewhere):
# ls -lU `kpsewhere -engine=pdfetex cont-en.fmt`
or
# kpsewhere -engine=pdfetex cont-en.fmt | xargs ls -Ul
-Sanjoy
`Never underestimate the evil of which men of power are capable.'
--Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
next prev parent reply other threads:[~2006-09-30 21:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 13:45 Jeremy Johnson
2006-09-29 17:35 ` John R. Culleton
2006-09-29 17:45 ` Steve Peter
2006-09-29 17:53 ` Taco Hoekwater
2006-09-29 21:27 ` Jeremy Johnson
2006-09-30 6:52 ` Taco Hoekwater
2006-09-30 13:55 ` Sanjoy Mahajan
2006-09-30 20:21 ` Jeremy Johnson
2006-09-30 21:02 ` Sanjoy Mahajan [this message]
2006-10-01 19:41 ` Mojca Miklavec
2006-10-01 20:49 ` Newbie question: Different PDF-output with pdftex versus tex - ghostscript Robert Kroon
2006-10-02 9:06 ` Martin Schröder
2006-10-02 13:16 ` Problem with ConTeXt installation gnwiii
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=E1GTlyG-0001Im-00@skye.ra.phy.cam.ac.uk \
--to=sanjoy@mrao.cam.ac.uk \
--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).