It seems Ghostscript 7.07.1 look for the library libcrypto.so.0.9.6 and doesnt realize I have infact updated to 0.9.7. This is easily fixed with a symlink, but should probably be adressed some other way. Reproducible: Always Steps to Reproduce:
Why doesn't ghostscript use the "libcrypto.so" or "libcrypto.so.0" softling that already points to the correctl library? (Doesn't compile for me either because of that)
That is a very good question. It really should. It seems a lot of packages point directly to the libcrypto.so.X.X.X file instead of to the symlink. When I updated to 0.9.7 I had to reemerge a bunch of stuff to get it working again. At least they compiled though, which ghostscript does not. For now I just made a symlink called libcrypto.so.0.9.6 pointing towards libcrypto.so.0.9.7, and it seems to work fine.
It just struck me... if several programs are having this problem, maybe its the libcrypto.so symlink that hasnt been updated properly? I'm at work now, can't check it myself right now, but I will as soon as I get home.
run `revdep-rebuild`
