You built with the no-shared option. None of these are errors, they just
aren’t supported without shared library support.
As for the linking, the difference is a single (larger) executable or a smaller
executable plus a shared library. If lots of applications use the same shared
library, there is a space saving.
Pauli
--
Dr Paul Dale | Cryptographer | Network Security & Encryption
Phone +61 7 3031 7217
Oracle Australia
> On 4 Jun 2019, at 6:30 pm, shiva kumar wrote:
>
> Hi,
> when I am performing make test while building OpenSSL 1.1.1b I got error as :
>
> ../test/recipes/70-test_sslcbcpadding.t skipped:
> test_sslcbcpadding needs the dynamic engine feature enabled
> ../test/recipes/70-test_sslcertstatus.t skipped:
> test_sslcertstatus needs the dynamic engine feature enabled
> ../test/recipes/70-test_sslextension.t . skipped:
> test_sslextension needs the dynamic engine feature enabled
> ../test/recipes/70-test_sslmessages.t .. skipped:
> test_sslmessages needs the dynamic engine feature enabled
> ../test/recipes/70-test_sslrecords.t ... skipped: test_sslrecords
> needs the dynamic engine feature enabled
> ../test/recipes/70-test_sslsessiontick.t ... skipped:
> test_sslsessiontick needs the dynamic engine feature enabled
>
> what is meant by enabling dynamic engine feature ?
> can anyone please explain me ?
>
> I also got as
> ../test/recipes/90-test_shlibload.t skipped: Test only
> supported in a shared build
>
> is they any problem if I create a no-shared build ?
> how is the linking works in no-shared build comapred to shared build ?
> please explain me.
>
> Thanks and Regards
> Shivakumar
