Re: libtool does not recognize lib64 -- Update to Olly Betts' patch

[Ralf Wildenhues]

Hello, and sorry for the looong delay,

* Toshio Kuratomi wrote on Thu, Oct 21, 2010 at 08:18:58PM CEST:
> On Mon, Sep 20, 2010 at 2:17 PM, Toshio Kuratomi <address@hidden> wrote:
> > On Mon, Sep 20, 2010 at 10:25:06PM +0200, Ralf Wildenhues wrote:
> >> > Anything I need to do to get this looked at?
> >>
> >> I'm looking at it.  The patch has issues, the approach itself has issues
> >> too, and is definitely not ready for the upcoming release.
> >>
> >> Details when I have them sorted out.
> >>
> > No problem, thsanks for looking.
> >
> > /me Awaits list of things to work on :-)
> 
> 
> ping?  I'm happy to take up where Ollie left off to improve the
> approach but I need to know what the issues that need to be resolved
> are :-)  There were no mentioned issues (except first run speed) when
> Olly first proposed his patch:
> http://lists.gnu.org/archive/html/libtool-patches/2010-06/msg00146.html

I haven't tested it much, so it would be nice if somebody could try out a
few distros/versions.  On one system here, there are dangling links in
/usr/lib, and it seems to take *very* (I mean *really*) long for
ldconfig to finish (maybe even hang?).

The code mistreats cross-compilation, but the code we have now does that
in the same way, so no big difference.

The patch uses \? in sed which is unportable to non-GNU sed, but can be
replaced by \{0,1\} portably (when the s delimiter is also changed from
comma to, say, |):
  /sbin/ldconfig -N -X -v 2>/dev/null | sed 's|^\(/.*\):\( 
(.*)\)\{0,1\}$|\1|p;d'

(Ignore that Solaris sed won't cope, see above note about cross issues.)

Are there any distros where ldconfig is not in /sbin, or the output
format varies?  Should we consider using the old code as fall-back,
at least when ldconfig dies or errors out for some reason?

One big issue is that the patch will add the wrong bitness directories
to the search path also, which means that libtool will find libraries
wrongly, and if there are .la files there also easily cause link
failures and such.  I'm not exactly sure how to fix this.

I'm not sure if this list is exhaustive.

Thanks,
Ralf