[tex-live] libstdc++.so.6

Olaf Weber olaf at infovore.xs4all.nl
Sun Aug 14 11:49:21 CEST 2005

Karl Berry writes:

>     The binaries
>       cfftot1 mmafm mmpfb otfinfo otftotfm t1dotlessj t1lint t1reencode
>       t1testpage

>     in `bin/i386-linux' link to libstdc++.so.6 -- I don't have this, only
>     libstdc++.so.5, and my system is a bit older than a year.

> I took a look today at importing the --with-cxx-runtime-hack stuff from
> web2c, which statically links libstdc++, with lcdf-typetools.  Anything
> is possible, I suppose, but it is not exactly straightforward.
> lcdf-typetools uses Automake, and for the hack to work, it obviously has
> to change the link command.  The result would not be pretty from the
> point of view of maintaining lcdftools, I'm afraid.

> Since we have always distributed the lcdftools binaries dynamically
> linked before, I am inclined to just keep doing that, despite it being
> suboptimal.  At least when Staszek builds the binaries, it will be
> against libstdc++ v5 instead of v6.

> Of course, if anyone has any suggestions or time to investigate further,
> that would be welcome.  For the record, the configure code is around
> line 185 of web2c/configure.in
> (http://tug.org/texlive/devsrc/Build/source.development/TeX/texk/web2c/configure.in)
> (search for runtime_hack), and then it's used in (among other places),
> the pdfetex: rule in pdfetex.mk
> (http://tug.org/texlive/devsrc/Build/source.development/TeX/texk/web2c/pdfetexdir/pdfetex.mk).

FWIW, the IRIX build of lcdf-typetools with MIPSpro compilers is
broken, because it uses 'ar' to create some convenience libraries,
where 'CC -ar' is required to get some C++ templates properly

Using libtool might resolve this, but being lazy about this I just
have my own buildscript that uses 'sed' after configure to fix up the
makefiles in question.

I need to do something similar with the xdvi makefile, as the
configure script happens to find iconv on the machine I build on, but
shouldn't be linking against it, and the most convenient way to
suppress this again turned out to be to edit the generated makefile.
(Another way would be to set up a chroot build environment.)

While this kind of quick and dirty hack is definitely not ideal and
somewhat fragile, it does have the advantage of being implementable on
short notice, and without requiring a rewrite of the auto* stuff of
lcdf-typetools itself.

Olaf Weber

               (This space left blank for technical reasons.)

More information about the tex-live mailing list