[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#240231: tetex-bin: mktextfm fails to create font



Gianluca Della Vedova <gianluca.dellavedova@unimib.it> wrote:

> Il dom, 2004-03-28 alle 11:45, Frank Küster ha scritto:
>> Gianluca Della Vedova <gianluca.dellavedova@unimib.it> schrieb:
>
>> Ah, I looked more closely: The file you sent last consists of two
>> outputs concatenated. The first one is from a different script, and I
>> can't see a clear error message in it. After it runs mf-nowin, the
>> output just stops. Then comes the output of an other call of mktexmf,
>> and this is now the one shipped with tetex. But it starts with "set -e",
>> just as before.
>> 
>> I fear we won't be able to find that bug, as long as you don't find out
>> which script is really called, and you do set -x, but not set -e in that
>> one. 
>
> I believe that the called script is /usr/share/texmf/web2c/mktex.opt

Oh, don't do that! - Well, I confused you, and you did your best to
confuse me, but eventually didn't manage to. Let's sort things:

- You call "mktextfm ecrm1095"

- This script calls mf-nowin, and this in turn calls mktexmf. Note the
  difference: mktexMF, not mktexTFM. It is this script which eventually
  fails in line 92.

  The output you sent the first time was with "set -ex" in mktexMF
  (which wasn't as good as I thought because -e breaks it otherwise);
  the output you sent the second time was from with "set -x" in mktexTFM
  - this is what confused me.

- mktextfm, mktexmf and a lot of other scripts that are implicitly
  called in these all source mktex.opt. By setting "set -x" in this
  file, the output generated was from all of these scripts, from the
  point where each sourced mktex.opt.

  This didn't make debugging easier; it would have been better to do
  "set -x" only in mktexMF. Well, but I digged through it.

The script changes dir to /var/cache/fonts/source/jknappen/ec and wants
to write to mf$$.tmp there, and this is what fails.

It shouldn't fail, because in /var/cache/fonts everybody should have
write permissions (with sticky bit set). But you say that even for root
it fails. Please give us the output of

 ls -ld /var/
 ls -ld /var/cache/
 ls -ld /var/cache/fonts/
 ls -ld /var/cache/fonts/*

Regards, Frank

-- 
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie




Reply to: