I had the same type of error and it was caused by the fact that some Debian package had a dependency that installed an older automake, so I had two automake packages installed. I think what I did to fix it was install a fake automake package (I made it with the equivs package) to replace the older automake and then I was able to compile Licq from CVS.
When I installed the newer GnuPG (ver 1.9.5) I had to upgrade libgcrypt packages and that broke Samba and CUPS, which I had to recompile. It seems I did not need the newer GnuPG package after all because the GnuPG feature in the CVS Licq seems to work even without gpg-agent. I removed the GnuPG 1.9.5 package and I am using the stable version of GnuPG. -- Andrew On Tue, 30 Mar 2004 10:52:25 +0200 Thomas Reitelbach <[EMAIL PROTECTED]> wrote: > > Hello Richard, > > you've probably mixed up several versions of autoconf/automake tools in your > > system. Please be sure that the correct version is used or remove the other > versions. > sometimes autoconf gets installed as "autoconf-1.5". please make sure that > "autoconf" then is a link pointing to the correct binary file. > > Thomas ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
