Thanks - I found the hint in INSTALL on howto create the shared files. What
I have not figured out is how to make openssl want them to be
libssl.a(member) and libcrypto.a(member).
Here is where I am atm:
I was able to create libssl.so.0.9.8 and libcrypto.so.0.9.8
The traditional packaging on
The error message:
exec(): 0509-036 Cannot load program wget because of the following errors:
*0509-022 Cannot load module /usr/lib/libssl.a(libssl.so.0.*
*9.8).*
0509-150 Dependent module libcrypto.so could not be loaded.
0509-022 Cannot load module libcrypto.so.
pressed send too soon, wanted to press bold again.
The hack to the error message is to copy libcrypto.so to /usr/lib. Then
it gets found and programs load.
What I would like is for the caller (in libssl.so) to request the search
for a member in a library rather than as a module(name) only.
It is
On Mon, 2014-08-04 at 22:45 +0200, Michael Felt wrote:
And finally - read exactly what is there: -- Dependent module libcrypt.so could
not be loaded, not as above
0509-150 Dependent module /usr/lib/libssl.a(libssl.so.0.9.8) could
not be loaded. (libssl.a(member))
The problem there is
To generate a .a of shared objects instead of static objects, really all you do
is build the shared object(s) and create an archive out of them. There is no
special magic about it beyond creating the shared object in the first place.
When linking a new program to an archive of shared objects,
I was - perhaps - not clear enough. Want I want is all the .o files
together in a single file that can be a single member of an archive.
Using the ./config shared got it to make .so files with everything
combined - but not, by default, that the .so files expect dependancies
in another
On 8/4/2014 7:06 PM, Sands, Daniel wrote:
To generate a .a of shared objects instead of static objects, really all you
do is build the shared object(s) and create an archive out of them. There is
no special magic about it beyond creating the shared object in the first
place. When
I don't understand what you mean by but not, by default, that the .so files
expect dependancies in another archive(member) search request. It sounds like
the core of your issue is that you're trying to build AIX shared libraries, so
you need to configure shared. If that's producing .so files