Re: buildconf on debian any workarounds?

Hi , tricky indeed :D I made sure I had the same versions as yourself with the same results. Then after seeing on a google a ref to aclocal --print-ac-dir noticed that the ac dir was in fact wrong (had to symlink /usr/local/share/aclocal to /usr/share/aclocal) That solved my original issue with AC_PROG_LIBTOOL , but now I get stuck at AC_MSG_ERROR.... I also tried Andrei's advice in another thread ...

XANFIRE:/root_old/php-gtk/php-gtk# sh -x /root_old/php-5.0.3/scripts/phpize

which does call aclocal but I still get configure.in:22: error: possibly undefined macro: AC_MSG_ERROR ...etc The thing that PUZZLES me most is why when I ./buildconf --force for PHP-5.0.3 itself I get no such errors ??? & AC_MSG_ERROR must be defined somewhere as it gets called if I deliberately break ./configure So if it works for PHP5 itself surely it can't be my automake/autoconf/libtool versions that are the issue ? if that makes sense where would I start looking to fix ? I have done a fair bit of googling but obviously I am out of my depth at this level... a starter for 10 would be the answer to where AC_MSG_ERROR is defined or is it internal to aclocal or whatever , or why does it work for PHP5 itself ? Regards, Simon. Markus Fischer wrote:

Hi, yes its really tricky on debian. I'm fighting it every time I install it new and try not to modify my environment once it works. However one thing for me was pretty sure that I need automake 1.9 (currently 1.9.5). autoconf is 2.59, libtool is 1.4.3, flex is 2.5.4 (flex-old package). HTH Simon Wheeler wrote:

Hi , I am having problems with buildconf on debian, I see the error probably relates to versions of autoconf,automake & libtool though I have to use autoconf >=2.5 for other (xandros) dependecies. automake & libtool are correct versions 1.4 && 1.4.3. [Last time I tried I had no such issues on Fedora & it compiled out of the box]

configure.in:65: error: possibly undefined macro: AC_PROG_LIBTOOL

     If this token and others are legitimate, please use m4_pattern_allow.
     See the Autoconf documentation.

Any workarounds or ideas for a non-hardcore linux user? Regards, Simon.