Re: g++ is not used by libtool

[Ralf Wildenhues]

Hi Christoph,

* Christoph Bartoschek wrote on Tue, Jun 07, 2005 at 10:39:57PM CEST:
> Am Dienstag, 7. Juni 2005 21:31 schrieb Ralf Wildenhues:
> > * Christoph Bartoschek wrote on Tue, Jun 07, 2005 at 08:57:26PM CEST:
> > >
> > > The problem is that fam is a C++ library and libtool is not capable of
> > > C++.
> >
> > Libtool /is/ capable of C++.
> 
> Oh, I want to apologise for writing this sentence.

No worries.  It's only to make this clear for people that search the
archives later.  :)

> > > How can I achieve that  g++ is called and not gcc?  And how to get rid
> > > of  /usr/lib/libstdc++.so correctly?
> >
> > Tell the maintainers of that package to use an up to date libtool.
> > Or update it yourself (1.5.18 is recent, you need to re-libtoolize
> > for ltmain.sh and get aclocal to include the corresponding libtool.m4
> > into aclocal.m4).
> 
> Is this easy to do? I guess I have to read libtools documentations.

If your systems installed versions of the Autotools
(Autoconf/Automake/Libtool) are recent, you should get away with
  libtoolize --force --copy
  aclocal
  automake --add --copy
  autoconf

This is how I got through with the very package you mentioned.

> > After all of this you should be set.  Well, you won't, because the rest
> > of the package is as unmaintained as the build infrastructure (the C++
> > standard conformance is rather, um, could be better).  Are you sure
> > there is not a more recent version of this package?
> 
> There is a more recent version 
> ftp://oss.sgi.com/projects/fam/download/stable/fam-2.7.0.tar.gz.  But it 
> also has the same problems, although it is from 2003. 

Well, tell them to update the tools they ship.

> I would like to omit this package, but KDE somehow depends on it and their 
> libtool finds /usr/lib/libstdc++.la, if I do not provide my own version.  
> But I have to prevent that any package uses /usr/lib/libstdc++.so.   

Let's see about this problem after you updated.

Regards,
Ralf