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 linking a new program to an archive of shared objects, and if > you didn't specify an import file, AIX will just use the standard static > object rules when it searches an archive for likely candidates to link in: > First logical member of the archive that has the desired symbol will be > chosen for inclusion. The difference is that the static linker will see the > "shared" flag and just add that member of the archive to the file's dynamic > loader table instead of statically linking it in. >On Mon, 2014-08-04 at 23:00 +0200, Michael wrote: 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 archive(member) search request. Yes, and you still create the archive version in the same way as if you were adding .o files. Something like: ar cruv libopenssl.a libopenssl.so.1.0.1 libopenssl.so.0.9.8 ... That's what I mean that there is no special magic to it.
