On 6 Mar 2008, at 02:05, Bob Friesenhahn wrote:
On Thu, 6 Mar 2008, Ralf Wildenhues wrote:That sounds a little harsh. I think that the LZMA complaint fromautomake may be because libtool requests a lzma package and it requiresthe very latest automake to do so.Where does Libtool 2.2 require lzma? That would be a serious bug, requiring such a recent Automake.I was not able to find where libtool 'requests' a lzma package but I do see that all of the Makefile.in files in the distribution include a target for it (dist-lzma).
Libtool was bootstrapped using Automake-1.10.1, but there is no reason that users of Libtool-2.2 need to use it too. I was careful to build the lzma release files by hand to compensate for not offering xdeltas or diffs -- and didn't introduce a dependency on the lzma rules to libtool-2.2 so that compatibility with older
Automakes wasn't compromised.
The reported error message seems quite strange, particularly since LZMA is in caps.
I agree with Peter's diagnosis... Nelson's Automake installation seews broken somehow: that's a perl failure in the Automake code AFAICT. The reported errors occur when am-subdir.at run Nelson's automake (which is at least version 1.10, judging by the
log messages.
Cheers,
Gary
--
())_. Email me: [EMAIL PROTECTED]
( '/ Read my blog: http://blog.azazil.net
/ )= ...and my book: http://sources.redhat.com/autobook
`(_~)_
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
