Author Michael.Felt
Recipients David.Edelsohn, Michael.Felt
Date 2016-02-29.10:05:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1456740340.96.0.340746547658.issue26439@psf.upfronthosting.co.za>
In-reply-to
Content
it was, partly, about the technical details - but I feel I have found the key bits - /full/path/libNAME.a(libNAME.so) + dlflags RTLD_NOW + RTLD_MEMBER for "native" AIX support.

Additionally, a patch should not break what might be working for some (via google I read of suggestions for other languages, e.g., java, where .so members are extracted or installed side-by-side with the .a archive) - as the IBM run-rime loader also accepts/looks for both .a and .so. And/or for when /sbin/ldconfig is available. And when available, is this used as last case, or preferred?

Lastly, we cannot assume we will know the name of the member based on the name of the library. In many cases, e.g., libiconv.a the IBM names are shr.o, shr4.o and shr4_64.o - and these are the only member names unless GNU libiconv.a has been added (and then libconv.a also contains libiconv.so.2 (so version support is also desired!)) in both 32 and 64 bit mode.

One technical detail I have not been able to discover yet: how to determine whether in 32-bit or 64-bit mode. This will be important for libraries that have shr4.o and shr4_64.o as the members that need to be dlopened.

Lastly: about adding the "stanza": python is a new language for me. Any assistance with a patch - to keep it properly 'pythonized'

In short, I shall continue my studies/learning. Assistance from anyone wiser than me is welcome!
History
Date User Action Args
2016-02-29 10:05:40Michael.Feltsetrecipients: + Michael.Felt, David.Edelsohn
2016-02-29 10:05:40Michael.Feltsetmessageid: <1456740340.96.0.340746547658.issue26439@psf.upfronthosting.co.za>
2016-02-29 10:05:40Michael.Feltlinkissue26439 messages
2016-02-29 10:05:39Michael.Feltcreate