Apparently, though unproven, at 19:08 on Wednesday 13 October 2010, James did
opine thusly:
> > # eix -e libtool
> > [I] sys-devel/libtool
> > Available versions:
> > (1.3) 1.3.5
> > (1.5) **1.5.26 (~)1.5.26-r1 2.2.6b **9999
> > (2) (~)2.2.8-r1 2.2.10{tbz2} **2.4
> > {test vanilla}
> > Installed versions: 2.2.10(2){tbz2}(12:30:40 10/06/10)(-vanilla)
> > Homepage: http://www.gnu.org/software/libtool/
> > Description: A shared library tool for developers
> >
> >
> > Do you have libtool:1.5 installed? Any effect?
>
> Looks like I have libtool 2.2.10 (like you) installed; should I mask
> the newer version and attempt a 1.5 installation?
>
> eix -e libtool
> [I] sys-devel/libtool
> Available versions:
> (1.3) 1.3.5
> (1.5) **1.5.26 ~1.5.26-r1 2.2.6b **9999
> (2) ~2.2.8-r1 2.2.10 **2.4
> {test vanilla}
> Installed versions: 2.2.10(2)(07:58:35 AM 10/03/2010)(-vanilla)
> Homepage: http://www.gnu.org/software/libtool/
> Description: A shared library tool for developers
>
> Won't that affect other packages, too?
389ds wants libtool 2.2.6b which is in SLOT 1.5.
You have 2.2.10 which is SLOT 2.
So they can install side-by-side without colliding.
You'd have to ensure 389ds uses the correct libtool and that other packages
don't get confused. I have no idea how to do that - every time I look into
libtool I come away thinking it's an unholy mess that should never have been
suffered to spawn. This directly results in my skills with it remaining at
zero.
--
alan dot mckinnon at gmail dot com
