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): libtiff-3.7.1-6
It looks like this issue has been solve upstream starting with tiff-3.7.2 tiff-3.7.3/ChangeLog says: 2005-01-11 Andrey Kiselev <dron> [snip] * 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 http://bugzilla.remotesensing.org/show_bug.cgi?id=733 and http://bugzilla.remotesensing.org/show_bug.cgi?id=730
Not worth an FC4 update, fixed in rawhide