libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Relink on AIX: Doesn't Just Work (TM)


From: Daniel Sands
Subject: Re: Relink on AIX: Doesn't Just Work (TM)
Date: Mon, 28 Jan 2008 17:07:53 -0700
User-agent: Thunderbird 1.5.0.12 (X11/20071018)

Yes, the 2.1 branch seems to fix this problem.  Woohoo!

Now for another request:  For dlopen on AIX, if you want to dlopen a shared library (.a not .so), you need to include the flag RTLD_MEMBER and append the name of the member .so to the name of the .a, in parentheses.  So to open libc, you would do:

    libcHandle = dlopen( "/usr/lib/libc.a(shr.o)", RTLD_MEMBER | RTLD_NOW);

I would like 1) support for this in Libtool's lt_dlopen library, and 2) a way to integrate this into the .la file.  The simplest method, which would be just fine with me, would be to name the internal object "shr.o" and append that in the case that the library name ends in .a.  But of course the LA could be extended to explicitly support this too, by supplying the member name and including a flag that this is a shared library and not a mere shared object.

Could these features also be included?

Thanks
Hello Daniel,

* Daniel Sands wrote on Thu, Dec 27, 2007 at 04:45:34AM CET:
  
When relink for install is done, any libs that are part of the same package
will be linked by their full installed path and not by -L,-l.  This is
because hardcode_direct is set to "yes".  It is true that if you specify a
library by its path, its path will be linked into the program or library.
But apparently for relinking libraries, libtool thinks this means that the
full path is supposed to be used instead of -L,-l   This doesn't work unless
the dependent .la's were already installed in their final install directory,
instead of for packaging.  I would suggest that unless some specific command
line option were used, AIX should use the libpath approach like most other
platforms use.
    

Around this issue, CVS HEAD Libtool has some changed behavior over
branch-1-5.  Could you try the former (you can download a nightly
snapshot tarball, see URL on the Libtool homepage), and if you still see
issues, please describe an example setup that fails?

HEAD also has a couple of DESTDIR tests that expose those setups that
can currently work with libtool (which does not include the most general
case, as can be seen in another recent report).

Thanks,
Ralf
Ralf


.

  


reply via email to

[Prev in Thread] Current Thread [Next in Thread]