# ldconfig ldconfig: libraries libcrypto.so.1.0.0 and libcrypto.so.10 in directory /usr/lib64 have same soname but different type. ldconfig: /usr/lib64/libcrypto.so.1.0.0 is not a symbolic link # ls -l /usr/lib64/libcrypto.so.10 lrwxrwxrwx 1 root root 27 Sep 20 2017 /usr/lib64/libcrypto.so.10 -> /usr/lib/libcrypto.so.1.0.0 The ebuild creates a symlink that is valid for the pre-17.1 profiles (where /usr/lib is a symlink to /usr/lib64), but now /usr/lib is a real dir with a different purpose. While this can easily be fixed manually, # rm /usr/lib/libcrypto.so.10 # ln -s /usr/lib64/libcrypto.so.1.0.0 /usr/lib64/libcrypto.so.10 it would be nice to have the ebuild edited to behave correctly under the newly stable profile (and, ideally, also still good for the old profiles). Reproducible: Always
dev-libs/openssl-1.0.2r doesn't create /usr/lib64/libcrypto.so.10. The timestamp of that link > Sep 20 2017 indicates an orphan file...
(In reply to Thomas Deutschmann from comment #1) > The timestamp of that link > > > Sep 20 2017 > > indicates an orphan file... I don't know how I missed that, my apologies.
