Guy Harris wrote:
> ...so the attached ":mksrc" may not actually be relevant to the problem.
My guess would be not.
> > $ :mksrc
> > Using `AC_PROG_RANLIB' is rendered obsolete by `AM_PROG_LIBTOOL'
> > You should add the contents of `/usr/local/share/aclocal/libtool.m4' to
> > `aclocal.m4'.
> > Running ./configure with no arguments. If you wish to pass any,
> > please specify them on the ./autogen.sh command line.
> > processing .
> > aclocal: configure.in: 120: macro `AM_PATH_GLIB' not found in library
>
> On what OS are you running this?
$ sh ./config.guess
i686-pc-sco3.2v5.0.5
$ autoconf --version ; automake --version; libtool --version
autoconf (GNU autoconf) 2.14a
Written by David J. MacKenzie.
Copyright (C) 1992, 93, 94, 96, 99, 2000 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
automake (GNU automake) 1.4
Copyright (C) 1999 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Tom Tromey <tromey@xxxxxxxxxx>
ltmain.sh (GNU libtool) 1.3.4 (1.385.2.196 1999/12/07 21:47:57)
> Did autoconf and automake come with the OS (and are thus presumably
> installed somewhere other than "/usr/local"), or were they installed
> under "/usr/local"?
$ whence autoconf automake libtool
/usr/local/bin/autoconf
/usr/local/bin/automake
/usr/local/bin/libtool
> autoconf/automake have an extremely irritating characteristic - they
> search *only* in the subtree in which they're installed, so that, for
> example, versions that come with the OS and that live in "/usr/bin"
> won't look under "/usr/local" for macros.
That is actually reasonable in that it is distributed with
*highly* versioned macros.
> If autoconf and automake were installed in "/usr/local/bin", but GTK+,
> say, was installed with the OS, you may have [a problem].
That is most likely the problem. In that case, you might
want to add some cruft to autogen.sh to verify that the
active autoconf will say something sensible to the blundering
neophyte :-). Thank you!