Thanks for the info Sascha, 

Would placing the libtool.m4 from libtool 1.4 into the system aclocal
tree cause any grief whilst compiling sources which don't require
libtool 1.4 and work with libtool 1.3.x

I am trying to create a sandboxed environment to assist in compiling PHP
out of CVS. I am not a PHP developer. Just a user who likes to test CVS
trees on a semi regular basis and since libtool 1.4 is not yet packaged
by any OS distribution as yet. I don't know the ramifications of
overwriting the system libtool/automake/autoconf toolchains

> On Thu, 24 May 2001, Yusuf Goolamabbas wrote:
> > I tried that. This is what I get whilst doing ./configure. My build tree
> > is separate from my source tree
>     From an email sent to this list on May 12:
>     I've removed ltconfig from cvs which should make it easier to
>     notice whether your libtool installation is broken.
>     If configure complains about not being able to find ltconfig,
>     it is a clear indication that aclocal has used the libtool.m4
>     of libtool 1.3.x to build aclocal.m4.  That is usually the
>     result of installing libtool with another prefix than
>     automake.
>     Running the following sequence of commands should cure that
>     (adapt to OS-specific commands as necessary):
>     a=`which aclocal`; b=`which libtool`; \
>     cp `dirname $b`/../share/aclocal/libtool.m4 \
>     `dirname $a`/../share/aclocal/
>     - Sascha                                     Experience IRCG

Yusuf Goolamabbas

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to