Re: multilib support

[Bob Friesenhahn]

On Fri, 31 Mar 2006, Simon Stelling wrote:

> Bob Friesenhahn wrote:
> > > Uhm, why is that a problem? If libtool did a check which ABI it's
> > > actually
> > > compiling/linking for, it could always prepend the appropriate path, no?
> >
> >
> > That sounds like a good plan.  Unfortunately, libtool does not appear to
> > check ABIs while linking.  Instead it uses the first library that it finds.
>
> I know, that's why I reported this bug :P Is there anything that prevents it
> from checking the current ABI and comparing it with the ABI of the library in
> question?

Anything is possible!  The main issue is when such capabilities can be 
delivered.  The release of libtool 2.0 is presumably very soon now so 
perhaps there is time for adding stop-gap work-arounds in well-known 
situations (e.g. Solaris & maybe Linux), but a later release of 
libtool would need to properly address multi-arch systems.

If the library architecture is encoded in .la files, then a utility 
could be developed to update existing .la files so they include the 
architecture.  Distributions which discard .la files would be at a 
disadvantage.

Bob
======================================
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/