On Wed, May 24, 2006 at 02:48:31PM +0200, Bruno Haible wrote: > Albert Chin-A-Young pointed me to this description of hardcode_direct_absolute > in the libtool CVS: > > _LT_TAGDECL([], [hardcode_direct_absolute], [0], > [Set to "yes" if using DIR/libNAME${shared_ext} during linking hardcodes > DIR into the resulting binary and the resulting library dependency is > "absolute", i.e impossible to change by setting ${shlibpath_var} if the > library is relocated]) > > The phrase "hardcodes DIR into the resulting binary" is misleading, because > > 1) This hardcoding affects only the given library dependency, not other > library dependencies. See execution trace below. In other words, it > hardcodes > the file name DIR/libNAME${shared_ext} in the resulting binary. > > 2) If DIR is a relative pathname, it is first made absolute before being > hardcoded in the binary. In other words, it's not DIR/libNAME${shared_ext} > which is hardcoded, but `cd DIR && pwd`/libNAME${shared_ext}.
Really? $ cc a.c /opt/TWWfsw/zlib11/lib/../lib/libz.sl $ chatr a.out ... shared library list: static /opt/TWWfsw/zlib11/lib/../lib/libz.sl.2 dynamic /usr/lib/libc.2 ... This is on HP-UX 11.23/PA. -- albert chin ([EMAIL PROTECTED]) _______________________________________________ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool