ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans van der Meer <hansm@science.uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: filepath on format generation
Date: Sun, 16 Dec 2007 17:28:27 +0100	[thread overview]
Message-ID: <78420A09-E03F-42F7-A73F-48F0C0835865@science.uva.nl> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2098 bytes --]

I migrated my texlive2007 tree to a new disk and now I encounter  
permission difficulties on context format generation. Calling the  
bashrc alias:

alias formats='texmfstart texexec --make en; texmfstart texexec --make  
--alone metafun

After the normal (error) messages about ls-R updating I get a  
permission error:

TeXExec | using search method 'kpsewhich'
TeXExec | updating file database
mktexlsr: Updating /Users/hans/Tex/texmf-private/ls-R...
mktexlsr: /usr/local/texlive/2007/texmf: directory not writable.  
Skipping...
<these are expected, no access for me to these directories>
mktexlsr: Done.
TeXExec | using tex engine pdftex
TeXExec | using tex format path ./pdftex
TeXExec | unable to make format due to lack of permissions

and on calling the following alias:

alias texversion='texmfstart texexec.pl --version; rm mpgraph.mp  
texvers-mpgraph.mp'

I get:

fmtutil: format directory `/web2c' does not exist.
kpathsea: Running mktexfmt context.fmt
fmtutil: format directory `/web2c' does not exist.

In my .bashrc I have:
# TeX variables
CONTEXT_RUBY=/usr/local/texlive/texmf-local/scripts/context/ruby
TEX_HOME=/usr/local/texlive/2007
TEXMFCACHE=/Users/hans/Temp
OSFONTDIR=/Library/Fonts
TEXMFCNF=/usr/local/texlive/texmf-local/web2c
TEXMF="{/Users/hans/Tex/texmf-private,/usr/local/texlive/texmf- 
context,/usr/local/texlive/texmf-local,/usr/local/texlive/2007/texmf,/ 
usr/local/texlive/2007/texmf,/usr/local/texlive/2007/texmf-config,/usr/ 
local/texlive/2007/texmf-dist,/usr/local/texlive/2007/texmf-doc,/usr/ 
local/texlive/2007/texmf-var}"
TEXFORMATS=/usr/local/texlive/2007/texmf-config/web2c

nor did work:
TEXFORMATS=/Users/hans/.texlive2007/texmf-var/web2c/pdftex

The idea is to have the formats locally under .texlive2007 in my home  
directory.

Can someone enlighten me where the base of respectively ./pdftex and / 
web2c is supposed to be? I thought I did set my environment variables  
just as I did previously, when it worked. Why suddenly these  
apparently incomplete paths? I MUST have some pathvariable WRONG, but  
which one is it?

Hans van der Meer




[-- Attachment #1.2: Type: text/html, Size: 3889 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
___________________________________________________________________________________

             reply	other threads:[~2007-12-16 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16 16:28 Hans van der Meer [this message]
2007-12-17 10:51 ` 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=78420A09-E03F-42F7-A73F-48F0C0835865@science.uva.nl \
    --to=hansm@science.uva.nl \
    --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).