First, I confess I hadn't refreshed rrdtool 1.1.x from CVS in a few months. But I recently did so and encountered some problems with the automake/autoconf/libtool stuff. The correct versions of these software packages existed on the development system (Solaris 2.8), but autoconf still generated some errors with MACROS defined in libtool.m4. After some digging, I found this message in the libtool documentation (http://www.gnu.org/software/libtool/manual.html):
"When you invoke the libtoolize program (see Invoking libtoolize), it will tell you where to find a definition of AM_PROG_LIBTOOL. If you use Automake, the aclocal program will automatically add AM_PROG_LIBTOOL support to your configure script. Nevertheless, it is advisable to include a copy of libtool.m4 in acinclude.m4, so that, even if aclocal.m4 and configure are rebuilt for any reason, the appropriate libtool macros will be used. The alternative is to hope the user will have a compatible version of libtool.m4 installed and accessible for aclocal. This may lead to weird errors when versions don't match." I followed this suggestion and it solved the problem! Perhaps there is something non-standard about my development system, but this is general advice from the libtool documentation. Shouldn't we considering adding libtool.m4 to acinclude.m4 in RRDtool CVS? I realize this will have no impact on any user-distribution, but it could make things easier to other developers working with CVS. Jake Jake Brutlag Network Analyst TV Services -- Network Operations Microsoft MSN -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/rrd-developers WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
