Red Hat Bugzilla – Bug 167831
Do not link libtiff to libstdc++
Last modified: 2007-11-30 17:11:13 EST
Description of problem:
libtiff.so is linked to libstdc++
(try ldd /usr/lib/libtiff.so)
applications that link to libtiff (like for example emacs) then are also linked
to libstdc++ and must suffer a little performance penalty on startup and have an
extra 700KB+ mapping at runtime.
The only reason this is done is because of 2 little functions:
extern TIFF* TIFFStreamOpen(const char*, std::ostream *);
extern TIFF* TIFFStreamOpen(const char*, std::istream *);
AFAICT (at least on my FC4 installation) nothing uses the above 2 functions.
It might be a better idea to put these 2 functions in a separate library
libtiffxx so that all the C applications that use libtiff don't have to be
linked to libstdc++. This is not a binary compatible change though.
There is a --disable-c++ flag that disables adding the c++ functions to libtiff.so
Version-Release number of selected component (if applicable):
It looks like this issue has been solve upstream starting with tiff-3.7.2
2005-01-11 Andrey Kiselev <firstname.lastname@example.org>
* libtiff/Makefile.am: Place the C++ stream API in the separate
library called libtiffxx to avoid unneeded dependencies. Probably
there will be more C++ API in the future. As per bugs
Not worth an FC4 update, fixed in rawhide