[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Ignore hardcode_direct=yes if results in static lib entry
From: |
Ralf Wildenhues |
Subject: |
Re: Ignore hardcode_direct=yes if results in static lib entry |
Date: |
Wed, 17 May 2006 17:00:04 +0200 |
User-agent: |
Mutt/1.5.11 |
Hello,
* Albert Chin wrote on Wed, May 17, 2006 at 03:18:09AM CEST:
> The following patch addresses
> http://lists.gnu.org/archive/html/libtool/2006-04/msg00044.html. I
> added a new variable, hardcode_direct_static, to indicate if
> hardcode_direct=yes would hardcode a static library dependency. This
> impacts HP-UX/PA and AIX.
>
> Patch against HEAD.
This patch is missing a documentation update (doc/libtool.texi).
I'm not sure whether it should be backported, probably not.
Does the testsuite pass with this?
Cheers,
Ralf
> 2006-05-16 Albert Chin-A-Young <address@hidden>
>
> * libltdl/config/ltmain.m4sh, libltdl/m4/libtool.m4
> (_LT_LINKER_SHLIBS, _LT_LANG_CXX_CONFIG, _LT_LANG_F77_CONFIG,
> _LT_LANG_FC_CONFIG) [ aix4*, aix5*, hpux10*, hpux11* ]:
> Introduce a new variable, hardcode_direct_static, which
> would ignore hardcode_direct=yes if the result would create a
> static library dependency. Static library dependencies are
> immune to $shlibpath_var.
Re: Ignore hardcode_direct=yes if results in static lib entry, Albert Chin, 2006/05/17