#23693 [Opn->Bgs]: buildconf does not use libtool/automake/autoconf in other path than standard

ID: 23693 Updated by: sniper@php.net Reported By: bernhard at fuersten dot info -Status: Open +Status: Bogus Bug Type: Compile Failure Operating System: MacOS X 10.2.6 PHP Version: 4.3.2RC3 New Comment: FYI: You should NOT use buildconf unless you're using CVS checkout of the sources. You most likely don't have the correct versions of all the required tools anyway.. Anyway, this worked fine on one Macosx server I tried it on so it's just your PATH that is not correct. Previous Comments: ------------------------------------------------------------------------ [2003-05-19 04:53:28] derick@php.net I remember this working fine too, I'll have a look at it (to verify your claim). Derick ------------------------------------------------------------------------ [2003-05-19 04:35:28] bernhard at fuersten dot info Hi, since PHP 4.3.1 and the current PHP-dev you have to use at least libtool 1.4.3 to run buildconf. OS X comes with 1.4.2. So I installed an additional libtool, autoconf and automake in /usr/local/gnutools for use with PHP only. I set the PATH var in the shell to /usr/ local/gnutools/bin:$PATH to let buildconf first determine the additional libtool. This works fine in the current PHP-dev, but not in PHP 4.3.2RC3. It seems that build/ buildcheck.sh does a better job in PHP-dev.. Bernhard ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=23693&edit=1