Hello!
On AIX, with runtime linking (-brtl linker flag) enabled, the current way
how libtool creates shared libraries prevents any form of "soname" support,
as there is no way to have the runtime loader to load a different version of
some shared object (either standalone or as archive member) than
are very
> flexible, however,
> because no other operating system (to my knowledge) supports the same
> features, those features are not portable.
>
> HTH,
>
> Rob
>
> On Fri, Jan 21, 2011 at 8:19 AM, Michael Haubenwallner
> mailto:michael.haubenwall...@salomon.at>
On 01/22/11 17:41, Peter O'Gorman wrote:
> On 01/21/2011 08:19 AM, Michael Haubenwallner wrote:
>> Hello!
>
> Hi.
>
> Library versioning for AIX would be a great feature.
>
>>
>> After playing around with different ways[1], this is my proposed one,
>
On 01/23/11 07:31, Daniel Sands wrote:
The reasons to choose this way:
*) It is possible to dlopen() with or without a version number:
- dlopen("libNAME.so(shr.o)", RTLD_MEMBER), besides the preferred
- dlopen("libNAME.so.1(shr.o)", RTLD_MEMBER), and even
Hello again,
some updates regarding the '# autoload' property in general, as well as
in combination with both 32 and 64 bit shared objects in one archive:
On 01/21/11 15:19, Michael Haubenwallner wrote:
> *) Create the Import File "shr.imp", containing
>- this head
On 08/30/12 15:29, Perry Smith wrote:
> ... that you can have 32 bit objects (shared or not shared) and 64 bit
> objects
> in the same archive ...
> You can do similar tricks with executables and loadable kernel extensions.
Offtopic: How does this work with executables?
> Of topic slightly
On 08/29/2012 11:18 AM, Brice Goglin wrote:
> Hello,
>
> I cannot get ltdl to load plugins on AIX 6.1. I am compiling plugins
> with -module -avoid-version. libtool generates a ".so" but then embeds
> it inside a ".a" and it looks like it really wants me to use this ".a"
> since the ".so" doesn't
On 10/17/2012 11:41 AM, Gary V. Vaughan wrote:
> 1. libltdl as a standalone runtime loader wrapper
> 2. libtool.m4/ltmain.sh to generate the libtool script
While I don't care about such a split in general, ...
> I think (2) belongs better into Automake alongside the other tool
> wrappers it
Hi Michael,
On 01/19/2016 09:44 PM, Michael Felt wrote:
> L.S.,
>
> If I understand the documentation correctly libtool places non-shareable
> members (.o files) in the src directory
> and "shareable aka PIC objects in src/.libs". However, libtool makes only one
> size of objects - either 32-bi
