Hi Dmitry, On 15-02-18 09:00, Dmitry Belyavsky wrote: > Hello, > > I get problems building and installing OpenSSL 1.1.0g from source. I > use Debian Wheezy (oldstable). > > After running ./config; make; make test; sudo make install > > I call /usr/local/bin/openssl > > I get an error > > /usr/local/bin/openssl: error while loading shared libraries: > libssl.so.1.1: cannot open shared object file: No such file or directory > > $ ldd /usr/local/bin/openssl > libssl.so.1.1 => not found > libcrypto.so.1.1 => not found > > This behavior differs from the one for version 1.1.0b, where > everything works fine. > > According to CHANGES in 1.1.0c > > *) Removed automatic addition of RPATH in shared libraries and > executables, > as this was a remainder from OpenSSL 1.0.x and isn't needed any more. > [Richard Levitte] > > Could you please clarify why this changes were introduced? RPATH has certain semantics which are unexpected for some users (e.g., copying files around and updating ld.so.conf won't work). They have their uses, but a build system using them *by default* is not necessarily a good idea. > Shouldn't the INSTALL file be changed to document this change > because the proposed way ( ./config; make; make test; make install) > does not work? It should, but you may have to check your dynamic linker configuration to make sure that the library in which libssl is installed is found in your library search path. Check /etc/ld.so.conf (and directories included from that file, if any) to make sure that it contains the directory where libssl.so ends up. If it does not, add it, and then run 'ldconfig' without arguments to update the cache. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users