Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
Assorted packages, most notably evince, need a shared version of libkpathsea, installed by tetex. The reason that a shared version of libkpathsea isn't installed is that tetex uses it's own libtool, rather than the standard libtool. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created an attachment (id=68059) [details] Patch to make shared libkpathsea Here is a patch to tetex to make a shared libkpathsea by using the stock libtool, rather than the one local to tetex. I've tested this locally, and it works fine, and enables evince to use the resulting shared lib.
Fixed in CVS.
Please reopen this bug, it's not completely fixed. upgrading from tetex-3.0-r2 to tetex-3.0-r3 I've seen a strange error about error during installation, skipping. cd /var/log/portage && grep error 8378-tetex-3.0-r3.log shows some lines like: kpsewhich: error while loading shared libraries: libkpathsea.so.4: cannot open shared object file: No such file or directory libkpathsea.so.4 seems to be a symlink to libkpathsea.so.4.0.0, but it seems to be created only after the error occurred. I'll attach the full log of this emerge. If I reemerge tetex-3.0-r3 the error is not present because this second time libkpathsea.so.4 is already installed in my system. But at the first run libkpathsea.so.4 is not found. Something like this appened with gettext-0.12 to 0.14 upgrade. The library path should be updated in order to find libkpathsea.so.4 during the installation.
Created an attachment (id=70741) [details] build log complete build log