I upgraded from the installed libtool 1.4.3 to libtool 1.5.10.
Now the only error message is:
Checking for python.
processing .
aclocal -I ./aclocal-fallback
Can't locate object method "path" via package "Request" at /usr/local/share/autoconf/Autom4te/C4che.pm line 69, <GEN1> line 308.
aclocal: autom4te failed with exit status: 1
Guy Harris writes:
In a message dated: Fri, 12 Nov 2004 13:18:32 PST
> richard.coe@xxxxxxxxxx wrote:
> > I retrieved the latest ethereal 0.10.7 and tried building it, and
> > I get the following errors with automake-1.9.2:
> >
> > Checking for python.
> > processing .
> > aclocal -I ./aclocal-fallback
> > aclocal:configure.in:13: warning: macro `AM_DISABLE_STATIC' not found in li
>brary
> > aclocal:configure.in:1195: warning: macro `AM_PROG_LIBTOOL' not found in li
>brary
>
> Those both sound libtool-related (the latter obviously; the former, from
> the "static", possibly).
>
> It might be that automake-1.9[.x] requires a newer version of libtool,
> e.g. one of the development releases.
>
> (The last time we upgraded to require a newer version of autoconf or
> automake - I forget which one started it - we ended up having to require
> newer versions of the other one of the two auto*'s, as well as a newer
> version of libtool. It's be Really Nice if the Web pages for each of
> those tools specified the minimum versions of the other two tools for
> the current version, and development versions, of the tool.)
>
> > I don't get these errors with automake-1.7.7
>
> Or it might be that, if you have two versions of automake installed, or
> you un-installed one and installed the other, that libtool's stuff is
> accessible to automake-1.7.7 but not to automake-1.9.2 (if both are
> installed, libtool might have installed its stuff in the place where
> automake-1.7.7 expects them to be, and that, as a result of being
> installed in a different location, e.g. under "/usr" vs. under
> "/usr/local", automake-1.9.2 isn't looking there).
--
Rich Coe richard.coe@xxxxxxxxxx
General Electric Medical Systems