Richard Levitte wrote:
>> Running LDD on the binaries in test/* shows that they appear to link
against
>> the "system" copies of libssl and libcrypto.
>>
>> Perhaps something I'm missing is setting up LD_PRELOAD or some such so
that
>> the tests run the local copy of
> On Feb 27, 2019, at 11:04 AM, Michael Richardson wrote:
>
> Running LDD on the binaries in test/* shows that they appear to link against
> the "system" copies of libssl and libcrypto.
With no environment overrides of LD_LIBRARY_PATH or similar, the test cases
in the build tree are expected to
On 27/02/2019 17:04, Michael Richardson wrote:
Running LDD on the binaries in test/* shows that they appear to link against
the "system" copies of libssl and libcrypto.
Perhaps something I'm missing is setting up LD_PRELOAD or some such so that
the tests run the local copy of libssl/libcrypto,
On Wed, 27 Feb 2019 17:04:09 +0100,
Michael Richardson wrote:
>
> Running LDD on the binaries in test/* shows that they appear to link against
> the "system" copies of libssl and libcrypto.
>
> Perhaps something I'm missing is setting up LD_PRELOAD or some such so that
> the tests run the local
Running LDD on the binaries in test/* shows that they appear to link against
the "system" copies of libssl and libcrypto.
Perhaps something I'm missing is setting up LD_PRELOAD or some such so that
the tests run the local copy of libssl/libcrypto, but I can't find that.
Am I missing something?
