libcrypto64.so.0.9.8 ( not loaded ). this is not in the aix machine. latest one libcrypto.so.1.0.0 is present in the machine

[karthi...@gmail.com]

Hi All,
I build openssl , fips ( openssl 1.0.2e) ( fips 2.0.11 ) versions.
The binaries were generated successfully. The list of required binaries for my work are
libcrypto.a
libcrypto.so
libcrypto.so.1.0.0
libssl.a
libssl.so
libssl.so.1.0.0
these are generally used to run my application on other platforms ( linux, solaris )
but on AIX i am getting an error

Dependent module /apps/clp/third_party/lib/openssl-fips/2.0/AIX64/libcrypto.a(libcrypto64.so.0.9.8) could not be loaded.
0509-152 Member libcrypto64.so.0.9.8 is not found in archive

I searched the machine, i dont have this libcrypto64.so.0.9.8.

Could you please help me to resolve this issue.
Apart from openssl i use curl build DLL's. The DLL's generated on this AIX machine are
libcurl.a
libcurl.la
libcurl.so.4
on other platforms there is another binary ( libcurl.so). But on this AIX machine it is not getting generated from curl build? does this have any effect to the above platform? the curl is built by giving ssl path which is above ssl.

Any inputs highly appreciated. I tried renaming libcrypto.so.1.0.0 to libcrypto64.so.0.9.8 still the error keeps on coming.
AIX 5.3 version

[Thomas Jahns]

On 02/08/2016 09:35 AM, karthi...@gmail.com wrote:
> Any inputs highly appreciated. I tried renaming libcrypto.so.1.0.0 to libcrypto64.so.0.9.8 still the error keeps on coming.
> AIX 5.3 version

AIX has two dynamic linking conventions, the more recent one is enabled by
adding -Wl,-brtl and once you have a library linked itself with this flag it's
recommended to also link all dependent objects with that flag. I mention this
because this flag is also specifically needed to pick up .so shared objects
before .a libraries optionally containing shared objects. But from your message
it looks more like some part of your build uses libcrypto from /usr/lib which
means you simply need to look out for a link line that does not specify
-L/apps/clp/third_party/lib/openssl-fips/2.0/AIX64.

Thomas

[Lőrinczy Zsigmond]

On 2016-02-08 09:35, karthi...@gmail.com wrote:

> Dependent module /apps/clp/third_party/lib/openssl-fips/2.0/AIX64/libcrypto.a(libcrypto64.so.0.9.8) could not be loaded.
> 0509-152 Member libcrypto64.so.0.9.8 is not found in archive

Is this the newly created fips, or the old one?
If the new one, then you might have forgot to add these:

LDFLAGS="-Wl,-brtl -L/path/where/new/libcrypto.lives"

or there library search path is not okay; check this:

dump -H -X32_64 exename

should be sg like this:

INDEX PATH BASE MEMBER
0 /usr/local/lib:/usr/lib:/lib
...

[karthi...@gmail.com]

This is newly built fips.
I build fips without using that LDFLAGS

i set LDFLAGS for builing curl libs. Is this required for fips/openssl also in AIX?

Thanks

[karthi...@gmail.com]

Hi,

As i understood that the dependencies and libs needs to be linked.
I tired linking libcrypto.a with libcrypto64.so.0.9.8
Even though, libcrypto64.so.0.9.8 is not there in the machine, i renamed libcrypto.so.1.0.0 to libcrypto64.so.0.9.8 and did a linking

This solved the problem.

Will there be any issue in future because of this step?
Thanks

[Lőrinczy Zsigmond]

Well, I don't know what 'fips' is, but whenever you compile something
from source, do these (use a script, there will be many repetions):

1. first set CFLAGS/CPPFLAGS/LDFLAGS/LIBS according to your system
2. decide configure options according to your system
3. then configure + make all + make install
4. examine the error-messages; do 'make distclean' and restart
5. when eventually it succeeds, check the files you got,
especially the shared libs versions and dependencies

eq if you have compiled openssl:

ls -l /path/to/bin/openssl # the new executable binary

dump -H -X32_64 /path/to/bin/openssl # its dependencies

# the new shared libs:

ls -l /path/to/lib/libcrypto*
ls -l /path/to/lib/libssl*

etc