"Steven Shaw" <[EMAIL PROTECTED]> wrote: > On 04/12/06, Jim Meyering <[EMAIL PROTECTED]> wrote: >> The problem is that your aclocal installation isn't finding libtool.m4. >> That may happen if you install/run your own version of autoconf (which >> contains aclocal). When aclocal runs properly, it puts a copy of >> the AC_PROG_LIBTOOL macro in the aclocal.m4 that it creates. > > I had to install my own autoconf because the one I had didn't work. > The aclocal comes from automake IIRC. I had to install a specific
Oops. Right. aclocal is from auto*make*, not autoconf <blush> > version of automake too. Is it that the automake doesn't know where to > look for the autoconf files? > >> If my guess is right, and in addition, you have a new enough >> distro-supplied version of autoconf installed, then running >> bootstrap like this might get you past the hump: >> >> env PATH=/bin:/usr/bin ./bootstrap > > Unfortunately my distros tools aren't the right version. I installed > my own versions of automake and autoconf to get over the humps. This > will defeat the purpose :) I think you said Debian. If so, you can safely use apt preferences (see man apt_preferences) to get automake, autoconf, and libtool from "unstable", which btw, doesn't deserve that name any more.
