Am cross compiling the FIPS enabled version for Android; In Android, some apps
are having trouble loading their bundled libcrypto library when the binary is
named as *.so.1.0.0 instead of libcrypto.so as platform library.
----- Original Message -----
From: Viktor Dukhovni <openssl-us...@dukhovni.org>
To: openssl-users@openssl.org
Cc:
Sent: Tuesday, April 21, 2015 11:47 PM
Subject: Re: [openssl-users] Building libcrypto/libssl without symbolic link
On Wed, Apr 22, 2015 at 12:12:45AM +0000, Shanku Roy wrote:
> lrw-r--r-- root root 2015-04-10 02:33 libcrypto.so ->
> libcrypto.so.1.0.0
> -rw-r--r-- root root 1988088 2015-04-10 02:27 libcrypto.so.1.0.0
>
> Is there any configure option in OpenSSL build scripts to not generate
> the symbolic links and rather generate actual binary as
> libcrypto.so/libssl.so from the build process like following:
The library "soname" is part of the ABI. What platform are you
building for where it would not be appropriate to encode the ABI
compatibility name into the library name?
--
Viktor.
_______________________________________________
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
_______________________________________________
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
