libusb-0.1.10a compilations fails if /usr/lib/ligosp.so if not symlinked to libosp.so Reproducible: Always Steps to Reproduce: 1. check if /usr/lib/libosp.so.3 doesn't NOT exist 2. emerge dev-libs/libusb-0.1.10a Checking and/or creating the symlink before compilation may be the one solution.
libusb-0.1.10a is looking for libosp.so.3 where I have is libosp.so.4 Need help
Create a symlink: ln -s /usr/lib/libosp.so /usr/lib/libosp.so.3
you have problems with your local install. run revdep-rebuild to make sure there aren't any broken reverse dependencies.
revdep-rebuild isn't installed on my system. Perhaps the people suggesting that should mention what ebuild provides the revdep-rebuild tool. adding symlinks between different major versions of the library is a bad idea. There are many other bugs about a missing libosp.so.3. The solution seems to be to recompile the tool that is compiled against the now-missing libosp.so.3. ldd will reveal if a particular binary is dynamically linked against libosp. I use the epm tool (from the epm package) to figure out what package owns the malfunctioning tool so I can rebuild it: epm -qf /usr/bin/openjade Look at the command that was issued just before the error to figure out which tool was dynamically linked against the missing library.