[openssl-users] Vanilla OpenSSL uses sytems libs
etc at coderhacks.com
etc at coderhacks.com
Wed Mar 14 09:59:20 UTC 2018
Yes... thats the same what I thought.
I expected to link against the the vanilla built if I set no-shared.
But it links against my systems libs.
It seems config takes my no-shared correctly - because If I do a typo it
will tell me about an unknown option.
Only If I set LD_LIBRARY_PATH to my vanillas path then it links against
the just built libs.
Are there more parameters than no-shared that influence that??
Thanks!
Chris
On 2018-03-14 10:54, Richard Levitte wrote:
> Something here makes no sense at all... you configure with
> 'no-shared', and then get an apps/openssl that's linked with the
> system shared libraries?
>
> In message <323c64fe-c3a7-0b93-a11e-46f743b999be at coderhacks.com> on Tue, 13 Mar 2018 23:46:14 +0100, "etc at coderhacks.com" <etc at coderhacks.com> said:
>
> etc> Hi!
> etc>
> etc> I put a vanilla OpenSSL in a local folder and compiled it.
> etc>
> etc> ./config no-shared
> etc> make
> etc>
> etc> I will not do a "make install" because I will keep my distros
> etc> installation.
> etc> But Iwill use the vanilla for tests. So I need the binary as well as
> etc> the libs.
> etc>
> etc> After a ldd I see that the apps/openssl as well as the libssl and
> etc> libcrypto use the systems OpenSSL-libs instead of the one I just
> etc> compiled.
> etc>
> etc> Is there an option so the makefile will produce binaries out of its
> etc> own libs instead of the sytems?
> etc>
> etc> Thanks!
> etc>
> etc>
> etc>
> etc>
More information about the openssl-users
mailing list