[tex-live] xindy now in build

Joachim Schrod jschrod at acm.org
Thu Mar 27 02:55:04 CET 2008

stefan-husmann at t-online.de wrote:
> Hello,
> my build of xindy produces a xindy.run the following libraries involved:
> [~]# ldd /usr/lib/xindy/xindy.run
> 	linux-gate.so.1 =>  (0xb7fa0000)
> 	libreadline.so.5 => /lib/libreadline.so.5 (0xb7f51000)
> 	libncurses.so.5 => /lib/libncurses.so.5 (0xb7f0e000)
> 	libm.so.6 => /lib/libm.so.6 (0xb7ee8000)
> 	libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7eb6000)
> 	libdl.so.2 => /lib/libdl.so.2 (0xb7eb2000)
> 	libsigsegv.so.0 => /usr/lib/libsigsegv.so.0 (0xb7eaf000)
> 	libc.so.6 => /lib/libc.so.6 (0xb7d6e000)
> 	/lib/ld-linux.so.2 (0xb7fa1000)
> postgre is not installed at all on my computer.

The list of shared libraries is dependent on your CLISP 
installation, not on xindy. With Vladimir's configuration, the 
locally installed CLISP is taken, a plugin for that CLISP is 
compiled, and it's then linked into a new executable that has the 
distribution's system and the additional plugin. Thus, xindy.run 
needs all shared libs that lisp.run (the CLISP executable) needs as 

Depending on the distributor's choice of configuration and 
compilation options, lisp.run from the distribution's system has a 
wide variety of options compiled in -- well, or it hasn't. That's 
why Martins executable from openSUSE has so many shared libs -- the 
SUSE folks tend to compile in everything that's available under 
this sun. (This is no slight against them, I run SUSE myself.) 
Whereas other folks choose to package much less options in their 
distribution's executables. That's the case in your installations. 
Some go so far (e.g., HP-UX, last time I looked) that support of 
external plugins is not packaged, or disabled.


Joachim Schrod				Email: jschrod at acm.org
Roedermark, Germany

More information about the tex-live mailing list