Re: aclocal: macro `AC_ADD_LIBPATH' defined in acinclude.m4 but never used
| From: | daemorhedron | Date: | Thu, 18 Apr 2002 19:17:28 +0000 |
| Subject: | Re: aclocal: macro `AC_ADD_LIBPATH' defined in acinclude.m4 but never used | ||
| References: | 1 | Groups: | php.gtk.general |
| Request: | Send a blank email to php-gtk-general+get-1808@lists.php.net to get a copy of this message | ||
Andrei : thanks so much for your fast response! Very impressive. =)
This info helped quite a bit too :
http://lists.php.net/article.php?group=php.gtk.general&article=1676
Once stepping down to php 4.1.2, php-gtk 0.5.0 worked just fine. The latest
CVS revision also seems to build, congifure, and compile just fine under php
4.1.2. I may attempt to get back up to php 4.2.0. My understanding is that
now that the so has been built, I could go back to 4.2.0 since the module
could still be used. It was just that 4.2.0 uses a different build process.
Again thanks for everything, hope this info helps someone. Keep up the great
work! =)
"Andrei Zmievski" <andrei@ispi.net> wrote in message
news:20020416090638.G9770@ispi.net...
> James Cameron wrote:
> > Tried a "make cvsclean", did a "cvs update" after removing all
> > .cvsignore files, confirming that my tree is empty of anything that
> > isn't from CVS. This fixed the previous issue ... and gave a new one;
> >
> > quozl:/usr/local/src/php-gtk$ ./buildconf
> > aclocal: macro `AC_ADD_LIBPATH' defined in acinclude.m4 but never used
> > aclocal: macro `AC_ADD_LIBRARY_WITH_PATH' defined in acinclude.m4 but
never used
> > aclocal: macro `AC_ADD_LIBRARY' defined in acinclude.m4 but never used
> > aclocal: macro `AC_ADD_INCLUDE' defined in acinclude.m4 but never used
>
> This is normal with the old PHP build system, which you are apparently
> using.
>
> > make: *** [buildmk.stamp] Error 1
> > quozl:/usr/local/src/php-gtk$
>
> This is probably coming from the line in buil2/build.mk, that says:
>
> test -f php_gtk.m4 && rm php_gtk.m4
>
> Can you run that by hand and see what it does?
>
> -Andrei
>
> It is commonly the case with technologies that you can get
> the best insight about how they work by watching them fail.
> -- Neal Stephenson