>> Strange indeed. Can you temporarily replace `mf2pt1` with a script >> that calls `strace`? Something like >> strace mf2pt1 ... &> ~/mf2pt1.strace.log >> You could then investigate in more detail which files `mf2pt1` tries >> to open and/or execute. >> > > [jcharles@pc1 mf]$ strace mf2pt1 feta11.mf &> ~/mf2pt1.strace > > generates the .pfb .pt1 and .tfm
Please try again with strace -ff -o ~/mf2pt1.strace mf2pt1 feta11.mf so that we can see the strace messages from `t1asm` also. Note that you will get at least two files called `mf2pt1.strace.XXXXX`, where `XXXXX` is a process ID. Werner
