Bug#389790: [Fwd: Re: changing tetex render engine]
This was discussed on the tex mailing list. I just wanted to forward it along. Basically all that needs be done to fix this bug is upgrade to the latest kpathsea. Thank you. -- Scott Henson LCSEE Systems Staff WVU MAE Undergraduate Ubuntu User --- Begin Message --- > as the default render engine for tex. I am having problems > with it in that it doesn't interpret environment variables > in the tex files. The old engine(etex) interpreted them This was not caused by switching the engine. It was caused by an implementation change in the kpathsea library. In the current sources of kpathsea / web2c, this is already fixed. Example (with teTeX-3.0): [EMAIL PROTECTED]:/tmp> cat ~/x.tex hi [EMAIL PROTECTED]:/tmp> /t/3.0/i/bin/i686-pc-linux-gnu/latex foo This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) entering extended mode (./foo.tex LaTeX2e <2003/12/01> Babel and hyphenation patterns for american, french, german, ngerman, b ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur kish, ukrainian, nohyphenation, loaded. (/space/gauss/TeX/3.0/i/share/texmf-dist/tex/latex/base/minimal.cls Document Class: minimal 2001/05/25 Standard LaTeX minimal class ) (./foo.aux) ! LaTeX Error: File `$HOME/x.tex' not found. ... Example (newer pdfetex, based on a newer kpathsea): [EMAIL PROTECTED]:/tmp> latex foo This is pdfeTeX, Version 3.141592-1.30.5-2.2 (Web2C 7.5.5) entering extended mode (./foo.tex LaTeX2e <2003/12/01> Babel and hyphenation patterns for american, british, french, german, n german, bahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esp eranto, estonian, finnish, greek, icelandic, irish, italian, latin, magyar, nor sk, polish, portuges, romanian, russian, serbian, slovak, slovene, spanish, swe dish, turkish, ukrainian, nohyphenation, loaded. (/software/oss/Text/teTeX-3.0/share/texmf-dist/tex/latex/base/minimal.cls Document Class: minimal 2001/05/25 Standard LaTeX minimal class ) (./foo.aux) (/home/te/x.tex) [1] (./foo.aux) ) ^^ Output written on foo.dvi (1 page, 200 bytes). Transcript written on foo.log. The shell is not envolved in expanding these environment variables. Thomas --- End Message ---
Bug#389790: [Fwd: Re: changing tetex render engine]
Hi all, "Scott J. Henson" <[EMAIL PROTECTED]> wrote: [about kpathsea in teTeX-3.0 not expanding environment variables in pathnames, like $HOME/foo.tex] > This was discussed on the tex mailing list. I just wanted > to forward it along. Basically all that needs be done to > fix this bug is upgrade to the latest kpathsea. Thank you. Thank you for the hint. Is there an isolated patch? You know, even if it wouldn't contradict Debian's customs, we wouldn't be able to incorporate a new version of the kpathsea library in Debian etch's teTeX - not enough manpower to do the work. Besides that, texlive-2005 is also in etch. I think it's a bug that it does not use the shared libkpathsea library, but its own version of kpathsea statically linked. But in this case it's a feature: The path expansion works when you install texlive instead of teTeX. Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Bug#389790: [Fwd: Re: changing tetex render engine]
Frank Küster writes:
> Hi all,
> "Scott J. Henson" <[EMAIL PROTECTED]> wrote:
> [about kpathsea in teTeX-3.0 not expanding environment variables in
> pathnames, like $HOME/foo.tex]
>> This was discussed on the tex mailing list. I just wanted
>> to forward it along. Basically all that needs be done to
>> fix this bug is upgrade to the latest kpathsea. Thank you.
> Thank you for the hint. Is there an isolated patch? You know, even if
> it wouldn't contradict Debian's customs, we wouldn't be able to
> incorporate a new version of the kpathsea library in Debian etch's teTeX
> - not enough manpower to do the work.
Usually there are no isolated patches for this kind of stuff. But
digging through the logs, this is likely what you want (no hard
guarantees though):
Index: tex-file.c
===
RCS file: /usr/local/cvsroot/texk/texk/kpathsea/tex-file.c,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -r1.69 -r1.70
--- tex-file.c 26 Aug 2004 21:30:13 - 1.69
+++ tex-file.c 21 Jun 2005 12:03:41 - 1.70
@@ -1,7 +1,7 @@
/* tex-file.c: high-level file searching by format.
+Copyright (C) 1998-2005 Olaf Weber.
Copyright (C) 1993, 94, 95, 96, 97 Karl Berry.
-Copyright 1998-2004 Olaf Weber.
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public
@@ -742,6 +742,9 @@
DEBUGF3 ("kpse_find_file: searching for %s of type %s (from %s)\n",
name, FMT_INFO.type, FMT_INFO.path_source);
+ /* Do variable and tilde expansion. */
+ name = kpse_expand(name);
+
/* Does NAME already end in a possible suffix? */
name_len = strlen (name);
if (FMT_INFO.suffix) {
@@ -850,6 +853,8 @@
ret = kpse_make_tex (format, name);
}
+ free((void*)name);
+
return ret;
}
> Besides that, texlive-2005 is also in etch. I think it's a bug that it
> does not use the shared libkpathsea library, but its own version of
> kpathsea statically linked. But in this case it's a feature: The path
> expansion works when you install texlive instead of teTeX.
I've seen issues with TeX-live and mismatched shared libraries because
versioning some libraries wasn't handled correctly. This is why
TeX-live should be built with the libraries in its source tree
statically linked, unless you have the manpower available to sort out
any issues resulting form shared linkage.
--
Olaf Weber
(This space left blank for technical reasons.)
Bug#389790: [Fwd: Re: changing tetex render engine]
Hi Olaf! On Don, 28 Sep 2006, Olaf Weber wrote: > I've seen issues with TeX-live and mismatched shared libraries because > versioning some libraries wasn't handled correctly. This is why > TeX-live should be built with the libraries in its source tree > statically linked, unless you have the manpower available to sort out > any issues resulting form shared linkage. For Debian the TeX live binaries are build on a mixed basis: --with-system-ncurses --with-system-pnglib --with-system-zlib --with-system-gd but the rest, especially libkpathsea, is used as in the sources. Do you expect problems from this? Best wishes Norbert --- Dr. Norbert Preining <[EMAIL PROTECTED]>Università di Siena Debian Developer <[EMAIL PROTECTED]> Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- `The best way to get a drink out of a Vogon is to stick your finger down his throat...' --- The Book, on one of the Vogon's social inadequacies. --- Douglas Adams, The Hitchhikers Guide to the Galaxy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389790: [Fwd: Re: changing tetex render engine]
Norbert Preining writes: > Hi Olaf! > On Don, 28 Sep 2006, Olaf Weber wrote: >> I've seen issues with TeX-live and mismatched shared libraries because >> versioning some libraries wasn't handled correctly. This is why >> TeX-live should be built with the libraries in its source tree >> statically linked, unless you have the manpower available to sort out >> any issues resulting form shared linkage. > For Debian the TeX live binaries are build on a mixed basis: > --with-system-ncurses --with-system-pnglib > --with-system-zlib --with-system-gd > but the rest, especially libkpathsea, is used as in the sources. > Do you expect problems from this? I don't recall the exact details, but this set shared libraries is likely safe. -- Olaf Weber (This space left blank for technical reasons.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
