On Sunday, 25 May 2008, at 10:21:30 (+0200),
Ralf S. Engelschall wrote:

> Sorry, bad expressed by me: I meant not that the system itself is
> ancient -- I wanted to say that the shipped Libtool is ancient.

Okay, fair enough.  But as a general rule, if a major distribution
holds off on upgrading, there's usually a good reason.  When *every*
major (RPM-based, at least) distribution holds off on upgrading,
there's usually a really, really good reason.

> Well, rpm5.org _TARBALLS_ are never a problem as they _CONTAIN_
> Libtool 2.2.4.

True, but being stuck with those tarballs makes it difficult for me to
contribute to CVS.

> The problem exists only if one is 1. building directly from CVS,
> 2. without using "devtool standalone" and 3. on a platform with an
> old Libtool 1.5.x provided by the system vendor. In all other
> situations one AFAIK doesn't have a problem.

I'm just saying, add me to that list. :)

I will try "devtool standalone" again; it failed last time I tried.

Michael

-- 
Michael Jennings (a.k.a. KainX)  http://www.kainx.org/  <mej@kainx.org>
Linux Server/Cluster Admin, LBL.gov       Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
 "To err is human; to really louse things up requires Microsoft
  products."                   -- Alexander Pope, slightly paraphrased