Re: Ignore hardcode_direct=yes if results in static lib entry

[Ralf Wildenhues]

> > >* 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.

I think this should be set for OpenBSD as well, no?

If I understand this correctly, then this setting will kill off one of
the biggest complaints the OpenBSD folks have against Libtool.  :-)

But say: do we actually know of systems that have hardcode_direct=yes
and that cause it to put the path into the DT_RPATH and not just the
full path in the DT_NEEDED?  If not, we don't need this new flag, and
reordering what we like to do in ltmain would be the better solution.

Oh well.  I put this patch off for a reason: it requires lots of
thought...

Cheers,
Ralf