On Thu, Nov 23, 2006 at 11:30:39AM +0100, Marcin Juszkiewicz wrote: > Dnia środa, 22 listopada 2006 18:43, Frank Küster napisał: > > Marcin Juszkiewicz <[EMAIL PROTECTED]> wrote: > > > > On this machine kpsewhich was stat-ing all files in filesystem > > > > Oh, this should not happen. Maybe some conffile setting is wrong? Can > > you please send the output of > > > > grep '^TEXMF =' /etc/texmf/texmf.cnf > [...] > kdebug:kpse_normalize_path (/home/hrw//texmf) => 1
It seems that $TEXMFHOME is expanding to /home/hrw//texmf with an extra slash in it, meaning that it's searching your entire home directory (a silly thing to do), so I suspect an extra slash somewhere here. You may have a corrupted/modified version of /etc/texmf/texmf.d/05TeXMF.cnf which is causing this. Could you please now also send the the output of: grep '^TEXMFHOME =' /etc/texmf/texmf.cnf echo $HOME > and here it start to go through filesystem and loops in kernel build due > to symlinks: > > kdebug:hash_lookup(/home/hrw/src/linux/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/debian/linux-image-2.6.19-rc2/lib/modules/2.6.19-rc2/source/drivers/infiniband/ulp) > => (nil) This is something which kpathsea is not designed to guard against. Hmm. Perhaps it should, say, keep track of any symlinks it meets in a path, and if it meets the identical symlink again, stop following it. That would require some significant changes to libkpathsea, though. Also, I believe this is quite a Unix-specific issue. Then again, symlink loops like this are just plain evil. Julian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
