Re: AIX TeTeX xdvi fails due to shared library problem
Martin Buchholz writes: > > It appears like xdvi.bin was built by someone named "rahtz", and not with > the standard AIX X11, but a non-standard /usr/local/X11R5. Note that > every time this binary is executed on any system, it will try to > access /home/scri95/users/, possibly invoking an automounter search... > I 'fess up. I built those AIX binaries. Never again, thanks! It was a nightmare. Maybe not all AIX systems are as screwy as the ones at SCRI, but I don't have access to any others. I presume this binary came from a TeX Live CD. The next incarnation has no AIX binaries on. if anyone has a contact at IBM who wants to donate an RS6000 to the TeXLive project, I'm listening. Sebastian Rahtz
Re: japan pictures
On Fri, 20 Apr 2001, Martin Buchholz wrote: > > "T" == Thomas Esser <[EMAIL PROTECTED]> writes: > > >> (martin@polgar) ~/i/resume $ xdvi tel.dvi > >> kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 pzdr > >> mktexpk: Running gsftopk pzdr 600 > >> gsftopk(k) version 1.17 > >> gs: No such file or directory > > T> You can set up mktexpk to use ps2pk instead of gsftopk (just look at > T> texmf/web2c/mktex.cnf). That way, you do not need gs. Or, install gs. > > Indeed, when used on a system with gs installed, xdvi does work. This > is reasonable. gsftopk might give a more explanatory error message > (as a naive user I don't understand why xdvi might need to invoke > ghostscript). > > >> Amazingly, this actually succeeded in printing a real telephone glyph! > > T> :-) > > >> But it shouldn't be this hard. Unfortunately, your experience is all too common. For many people, getting teTeX to work seems to be very painful. As a result, they become reluctant to make changes to their system. This means they don't install improved versions, bug fixes, etc. (or they give up on unix and buy Windows NT with Y&Y TeX!). > T> Well, for me, it just works. One problem is that you are using a > T> PostScript font without the "default" program that people use to handle > T> PostScript (gs + gv). The other way (ps2pk + xdvi) was not known to > T> you... :-( > > T> Of course, ps2pk *is* mentioned in TETEXDOC. The .pk fonts are a major headache. Ghostscript is rather fragile, in part because users are forever tweaking environment variables to change font paths, etc. (e.g., to switch between URW and Adobe versions of the lw35 fonts, add Japanese, ...). If you let users generate them you have problems of world writable directories, etc. Now that xdvi has a type1 rasterizer and we have some decent free fonts that support LY1 encodings, it may be possible for many people to live happily without ever using .pk fonts. If you are using Type 1 fonts, pdf may be less problematic. I ran pdflatex on the sample file. Xpdf on SGI Irix gave: Error: Failed to open font: '-*-zapfdingbats-medium-r-normal-*-11-*-*-*-*-*-*-*' Acrobat reader does work, as did gs. > But TETEXDOC is not mentioned on the teTeX Home Page. I'll go read it > now. > > Like many TeX users, I have one TeX document (my resume) which I > update every year or two. So I don't want to spend hours learning. > I already have my own buggy free software to maintain. If you are going to use TeX at all, you may find it better in the long run to use it for everything so that you keep your skills current and can rely on it in a crunch. Otherwise you may end up like the sad people who wander the halls looking for a way to load their old WordStar files that won't import into their copy of MS Office. The TeX files I created using WordStar on a CPM system will still work with today's teTeX, but many documents I created with the proprietary word processor du jour are lost forever. > teTeX was really easy to install - thank you - You've put together a > great distribution. I especially like the way that the distribution > can be installed in any directory. > > Perhaps ghostscript and ghostview should be included in the > distribution. My memories of the last time I built these programs > years ago were not altogether pleasant. This has been discussed before. A central problem is that the current version is not GPL'd, and many teTeX users do need (in fact, help to create) the new features. On some systems (SGI) DPS is provided, so not everyone needs gs. -- George White <[EMAIL PROTECTED]> Halifax, Nova Scotia
Re: AIX TeTeX xdvi fails due to shared library problem
> BTW: "rahtz" is of course *the* Sebastian Rahtz (who make TeX Live and > have written (with others) the LaTeX Companion books... I always knew he must be a group to do all that amazing stuff :) Karsten "never trust a quote you haven't faked yourself" Tinnefeld -- Karsten Tinnefeld [EMAIL PROTECTED] Fachbereich Informatik, Lehrstuhl 2 T +49 231 755-4737 Universität Dortmund, D-44221 Dortmund, Deutschland F +49 231 755-2047
Re: japan pictures
> "T" == Thomas Esser <[EMAIL PROTECTED]> writes: >> (martin@polgar) ~/i/resume $ xdvi tel.dvi >> kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 pzdr >> mktexpk: Running gsftopk pzdr 600 >> gsftopk(k) version 1.17 >> gs: No such file or directory T> You can set up mktexpk to use ps2pk instead of gsftopk (just look at T> texmf/web2c/mktex.cnf). That way, you do not need gs. Or, install gs. Indeed, when used on a system with gs installed, xdvi does work. This is reasonable. gsftopk might give a more explanatory error message (as a naive user I don't understand why xdvi might need to invoke ghostscript). >> Amazingly, this actually succeeded in printing a real telephone glyph! T> :-) >> But it shouldn't be this hard. T> Well, for me, it just works. One problem is that you are using a T> PostScript font without the "default" program that people use to handle T> PostScript (gs + gv). The other way (ps2pk + xdvi) was not known to T> you... :-( T> Of course, ps2pk *is* mentioned in TETEXDOC. But TETEXDOC is not mentioned on the teTeX Home Page. I'll go read it now. Like many TeX users, I have one TeX document (my resume) which I update every year or two. So I don't want to spend hours learning. I already have my own buggy free software to maintain. teTeX was really easy to install - thank you - You've put together a great distribution. I especially like the way that the distribution can be installed in any directory. Perhaps ghostscript and ghostview should be included in the distribution. My memories of the last time I built these programs years ago were not altogether pleasant.
Re: AIX TeTeX xdvi fails due to shared library problem
> OK, this is an attempt at a high-quality bug report. Successful, no question :-) > AIX's vanilla X11. No LD_LIBRARY_PATH. teTeX 1.0 recent download. > I believe xdvi.bin is incorrectly built. It should be built with AIX's > X11 and should have a RPATH of /usr/lib:/lib. I agree. Is there anybody with a rs6000/AIX4 platform where the release version is 4.1.4 (or older) who can build a fixed xdvi.bin and mfw from the teTeX-1.0.7 sources? One thing to note is that Xaw and Xmu should not be linked in dynamically (not all system have these libs installed). For xdvi.bin, the link-instructions are: ld -r /usr/lib/libXaw.a /usr/lib/libXmu.a -o nonshared.o -bnso gcc -o xdvi xdvi.o ... nonshared.o ... -lm (gcc could be replaced by a call to a different compiler or just the linker, nonshared.o replaces -lXaw -lXmu of the original link command). Thomas BTW: "rahtz" is of course *the* Sebastian Rahtz (who make TeX Live and has written (with others) the LaTeX Companion books...
AIX TeTeX xdvi fails due to shared library problem
> "T" == Thomas Esser <[EMAIL PROTECTED]> writes: >> (martin@aix) ~/i/resume $ LANG=C xdvi tel.dvi >> Could not load program xdvi.bin: >> Dependent module /usr/lib/libXt.a(shr.o) could not be loaded. >> Member shr.o is not found in archive >> >> >> Hmmm. A shared library build glitch. T> If this is the teTeX-provided binary, report this as a bug. Please, OK, this is an attempt at a high-quality bug report. T> mention the AIX release that you are using. Are you using the default T> X libraries that come with the system, or do you have "own" ones (and T> LD_LIBRARY_PATH set? AIX's vanilla X11. No LD_LIBRARY_PATH. teTeX 1.0 recent download. Let's take a look at the dynamic loading information. As you can see below, xdvi.bin is built to contain a bogus dynamic load path (RPATH). It appears like xdvi.bin was built by someone named "rahtz", and not with the standard AIX X11, but a non-standard /usr/local/X11R5. Note that every time this binary is executed on any system, it will try to access /home/scri95/users/, possibly invoking an automounter search... I believe xdvi.bin is incorrectly built. It should be built with AIX's X11 and should have a RPATH of /usr/lib:/lib. I don't believe any of the other platforms I'm using have this kind of problem. Self-explanatory shell transcript follows: (martin@aix) ~/i/resume $ xdvi tel.dvi Could not load program xdvi.bin: Dependent module /usr/lib/libXt.a(shr.o) could not be loaded. Member shr.o is not found in archive zsh: exit 255 xdvi tel.dvi (martin@aix) ~/i/resume $ which xdvi /project/mule/teTeX/bin/rs6000-aix4/xdvi (martin@aix) ~/i/resume $ ar tv /usr/lib/libXt.a rw-rw 2715/300 3872 Jun 16 04:13 1999 sharedlib.o rw-rw 2715/300 4257 Jun 16 04:13 1999 sharedlib_64.o rw-r--r-- 2/2 624928 Dec 8 12:16 1999 shr4.o rw-r--r-- 2/2 772522 Dec 8 12:16 1999 shr_64.o (martin@aix) ~/i/resume $ uname -a AIX aix 3 4 000B665D4C00 (martin@aix) ~/i/resume $ oslevel 4.3.0.0 (martin@aix) ~/i/resume $ env | grep LIB (martin@aix) ~/i/resume $ (martin@aix) /usr/bin/X11 $ dump -H =xdvi.bin /project/mule/teTeX/bin/rs6000-aix4/xdvi.bin: ***Loader Section*** Loader Header Information VERSION# #SYMtableENT #RELOCentLENidSTR 0x0001 0x0162 0x2ac2 0x0104 #IMPfilIDOFFidSTR LENstrTBLOFFstrTBL 0x0006 0x00022268 0x0ecf 0x0002236c ***Import File Strings*** INDEX PATH BASEMEMBER 0 /usr/local/X11R5/lib:/home/scri95/users/rahtz/lib/gcc-lib/rs6000-ibm-aix4.1.4.0/2.8.1:/home/scri95/users/rahtz/rs6000-ibm-aix4.1.4.0/lib:/home/scri95/users/rahtz/lib:/usr/lib:/lib 1libXt.a shr4.o 2libXt.a shr.o 3libc.a shr.o 4libX11.ashr.o 5libXext.a shr.o (martin@aix) /usr/bin/X11 $ dump -H =xterm /usr/bin/X11/xterm: ***Loader Section*** Loader Header Information VERSION# #SYMtableENT #RELOCentLENidSTR 0x0001 0x0159 0x0e65 0x0074 #IMPfilIDOFFidSTR LENstrTBLOFFstrTBL 0x0006 0xcd34 0x10d8 0xcda8 ***Import File Strings*** INDEX PATH BASEMEMBER 0 /usr/lib:/lib:/usr/lpp/xlC/lib 1libc.a shr.o 2libXt.a shr4.o 3libX11.ashr4.o 4libXext.a shr.o 5libcurses.a shr.o
Re: japan pictures
>
> \documentclass{article}
> \usepackage{pifont}
> \begin{document}
> \ding{37}
> \end{document}
>
Well, works for me on all systems that I have tested (Linux and Solaris).
LaTeX, dvips and xdvi: all no problem.
> (martin@lasker) ~/i/resume $ /usr/bin/latex tel.tex
> warning: kpathsea: No usable entries in /usr/share/texmf/ls-R.
> warning: kpathsea: See the manual for how to generate ls-R.
> This is TeX, Version 3.14159 (Web2C 7.2)
Well, a known bug. New GNU fileutils and old mktexlsr. They do not work
together. After that mktexlsr was released, the fileutils maintainer
have changed the output format of ls :-( New versions of mktexlsr
(e.g. teTeX-1.0) do work with GNU fileutils-4.
> LaTeX Font Warning: Font shape `U/pzd/m/n' undefined
> (Font) using `U/cmr/m/n' instead on input line 60.
Ok, this system misses a .fd file. In teTeX, these have always been
provided.
> (martin@aix) ~/i/resume $ LANG=C xdvi tel.dvi
> Could not load program xdvi.bin:
> Dependent module /usr/lib/libXt.a(shr.o) could not be loaded.
> Member shr.o is not found in archive
>
>
> Hmmm. A shared library build glitch.
If this is the teTeX-provided binary, report this as a bug. Please,
mention the AIX release that you are using. Are you using the default
X libraries that come with the system, or do you have "own" ones (and
LD_LIBRARY_PATH set?
> (martin@polgar) ~/i/resume $ xdvi tel.dvi
> kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 pzdr
> mktexpk: Running gsftopk pzdr 600
> gsftopk(k) version 1.17
> gs: No such file or directory
You can set up mktexpk to use ps2pk instead of gsftopk (just look at
texmf/web2c/mktex.cnf). That way, you do not need gs. Or, install gs.
> Amazingly, this actually succeeded in printing a real telephone glyph!
:-)
> But it shouldn't be this hard.
Well, for me, it just works. One problem is that you are using a
PostScript font without the "default" program that people use to handle
PostScript (gs + gv). The other way (ps2pk + xdvi) was not known to
you... :-(
Of course, ps2pk *is* mentioned in TETEXDOC.
Thomas
Re: WG: japan pictures (fwd)
Frank: Iris is the one I asked about a telephone glyph in latex years
ago, while hacking my resume.
I'd like to share my experiences as a naive user trying to get that
telephone glyph into my resume.
I created a small file for testing, tel.tex.
\documentclass{article}
\usepackage{pifont}
\begin{document}
\ding{37}
\end{document}
First, Linux:
(martin@lasker) ~/i/resume $ /usr/bin/latex tel.tex
warning: kpathsea: No usable entries in /usr/share/texmf/ls-R.
warning: kpathsea: See the manual for how to generate ls-R.
This is TeX, Version 3.14159 (Web2C 7.2)
(tel.tex
LaTeX2e <1998/12/01> patch level 1
(/usr/share/texmf/tex/latex/base/article.cls
Document Class: article 1997/10/10 v1.3x Standard LaTeX document class
(/usr/share/texmf/tex/latex/base/size10.clo))
! LaTeX Error: File `pifont.sty' not found.
Type X to quit or to proceed,
Ok, let's try another machine (Solaris):
(martin@aix) ~/i/resume $ latex tel.tex
This is TeX, Version 3.14159 (Web2C 7.2)
(tel.tex
LaTeX2e <1998/06/01>
(/usr/local/lib/tex/texmf/tex/latex/base/article.cls
Document Class: article 1998/05/05 v1.3y Standard LaTeX document class
(/usr/local/lib/tex/texmf/tex/latex/base/size10.clo))
(/usr/local/lib/tex/texmf/tex/platex/base/pifont.sty
LaTeX Font Warning: Font shape `U/pzd/m/n' undefined
(Font) using `U/cmr/m/n' instead on input line 60.
LaTeX Font Warning: Font shape `U/psy/m/n' undefined
(Font) using `U/cmr/m/n' instead on input line 61.
) (tel.aux) [1] (tel.aux)
LaTeX Font Warning: Some font shapes were not available, defaults substituted.
)
Output written on tel.dvi (1 page, 216 bytes).
Transcript written on tel.log.
Hmmm, that got further. It had the package, but apparently not the
font.
Detour to install teTeX 1.0.7
Let's try AIX:
(martin@aix) ~/i/resume $ latex tel.tex
This is TeX, Version 3.14159 (Web2C 7.3.1)
(tel.tex
LaTeX2e <1999/12/01> patch level 1
Babel and hyphenation patterns for american, french, german, ngerman, n
ohyphenation, loaded.
(/project/mule/teTeX/share/texmf/tex/latex/base/article.cls
Document Class: article 1999/09/10 v1.4a Standard LaTeX document class
(/project/mule/teTeX/share/texmf/tex/latex/base/size10.clo))
(/project/mule/teTeX/share/texmf/tex/latex/psnfss/pifont.sty
(/project/mule/teTeX/share/texmf/tex/latex/psnfss/upzd.fd)
(/project/mule/teTeX/share/texmf/tex/latex/psnfss/upsy.fd)) (tel.aux) [1]
(tel.aux) )
Output written on tel.dvi (1 page, 256 bytes).
Transcript written on tel.log.
Success!! But wait, a dvi file by itself is not enough...
(martin@aix) ~/i/resume $ LANG=C xdvi tel.dvi
Could not load program xdvi.bin:
Dependent module /usr/lib/libXt.a(shr.o) could not be loaded.
Member shr.o is not found in archive
Hmmm. A shared library build glitch.
(martin@aix) /usr/lpp/X11/lib/R6 $ ar tv libXt.a
rw-rw 2715/300 3872 Jun 16 04:13 1999 sharedlib.o
rw-rw 2715/300 4257 Jun 16 04:13 1999 sharedlib_64.o
rw-r--r-- 2/2 624928 Dec 08 12:16 1999 shr4.o
rw-r--r-- 2/2 772522 Dec 08 12:16 1999 shr_64.o
That shouldn't happen on a more
common platform. So back to teTeX on Solaris:
(martin@polgar) ~/i/resume $ xdvi tel.dvi
kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600 --dpi 600 pzdr
mktexpk: Running gsftopk pzdr 600
gsftopk(k) version 1.17
gs: No such file or directory
gs terminated abnormally with status 1
grep: pzdr.log: No such file or directory
mktexpk: `gsftopk pzdr 600' failed to make pzdr.600pk.
kpathsea: Appending font creation commands to missfont.log.
xdvi.bin: can't find font pzdr; using cmr10 instead at 600 dpi.
Oh well :-(
But we don't really need to use xdvi. We only need dvips.
(martin@polgar) ~/i/resume $ dvips -o tel.ps tel.dvi
This is dvips(k) 5.86 Copyright 1999 Radical Eye Software (www.radicaleye.com)
' TeX output 2001.04.20:1657' -> tel.ps
. [1]
That was easy.
But polgar doesn't have a gv. Back to Linux.
