Re: Bug in autoconf report

> Hi Jeroen, > > Did you ever get the problem sorted out? Has anyone encountered the > same difficulty? I installed brand new autoconf, automake and libtool into my $HOME. That solved the problem. However, I still don't know what the problem was, probably there were some library files not well installed. Anyway, I'm not the administrator of that computer, so I couldn't do much more than bugging sysop and/or install those tools in my homedir. The former one didn't help, the latter one did. The server I tried on was Debian, and in my original mail you can find the versions I had at that time. Currently, it is: buildconf: checking installation... buildconf: autoconf version 2.52 (ok) buildconf: automake version 1.5 (ok) buildconf: libtool version 1.4 (ok) <-- on purpose, read somewhere that some version was giving trouble, so I played on safe. rebuilding Makefile templates --Jeroen > > I just encountered the same issue in almost the same circumstances. In > my case, automake and libtool both live in /usr/bin. > > % cd php4 > % ./buildconf > buildconf: checking installation... > buildconf: autoconf version 2.13 (ok) > buildconf: automake version 1.4 (ok) > buildconf: libtool version 1.4.2 (ok) > rebuilding Makefile templates > rebuilding configure > autoconf: Undefined macros: > ***BUG in Autoconf--please report*** AC_TRY_DLOPEN_SELF > configure.in:162:AC_MSG_RESULT([$PHP_SAPI]) > configure.in:182:AC_MSG_RESULT([$php_cv_cc_dashr]) > [output truncated for brevity's sake] > > I am updating all of my Autotools - will try again when that is done. > > --zak > > On September 25, 2001 11:53 am, Jeroen van Wolffelaar wrote: > > > On Tue, 25 Sep 2001, Jeroen van Wolffelaar wrote: > > > > <snip> > > > > > > > > Note: after I solved that warning about automake & libtool not > > > > being in the same dir, the error remainded the same. (I copied > > > > the automake executable to the same dir as the libtool > > > > executable) > > > > > > Ok, but it's still a problem with your build tools, it works fine > > > here. You re-ran buildconf I guess? > > > > Yes, retrieving the whole CVS again takes quite some time again... > > what's the command to clean all files that are not from CVS, so that > > I've got a really clean tree again? make clean / make distclean? (But > > they don't yet work before you run configure...) > > > > So you think libtool is mal-installed? Could be possible... > > > > > Derick > > > > --Jeroen