Re: Using libtool for linking

[Benoit SIGOURE]

On Aug 17, 2007, at 8:42 PM, Jason Curl wrote:

> Peter O'Gorman wrote:
> > On Fri, 2007-08-17 at 13:29 +0200, Jason Curl wrote:
> >
> > > As for testing the situation, AC_CHECK_LIB makes me believe it  
> > > will work. But it only works in a subset of cases (i.e. static  
> > > only). I have another implementation that I can compile in but at  
> > > the moment there is no indication I should use my own internal  
> > > implementation (I'd rather use an external implementation where  
> > > possible in the belief it's probably been better debugged).
> > >
> > > So, ideas how to work around this problem to achieve my goal?
> > Why not import the libiberty sources into your project and build a
> > convenience libiberty.
> I'd rather use what's already installed.

This topic was already raised on this ML (although it was more  
Windows [Cygwin] centered):
http://lists.gnu.org/archive/html/libtool/2007-03/msg00022.html

I don't know the details but it looks like libiberty is very special  
and it seems troublesome to link a library against an installed  
version of libiberty so you should probably reconsider shipping a  
copy of libiberty with your sources (which is what is encouraged by  
the manual of libiberty) or not use libiberty at all.

http://lists.gnu.org/archive/html/libtool/2007-03/msg00024.html
"It is always built static by default even on ELF systems, for
the same reason as libiberty - it is not expected to expose anything
resembling a stable or maintained ABI.  And its maintainers do not want
the burden of having to maintain an ABI given its history of not being
designed as such."

http://gcc.gnu.org/onlinedocs/libiberty/Using.html
"To date, libiberty is generally not installed on its own. It has  
evolved over years but does not have its own version number nor  
release schedule."
which seems to confirm what's been said in the above reply.

Cheers,

--
Benoit Sigoure aka Tsuna
EPITA Research and Development Laboratory

PGP.sig
Description: This is a digitally signed message part