Re: Alpha?

On Jun 21, 2006, at 1:16 AM, Christian Weiske wrote:

If you have not in the standard dirs, buildconf needs to be run "--with-phpize=/path/to/phpize". If you forget this, you just get: -------------------- grep: /usr/local/include/php/main/php.h: No such file or directory grep: /usr/local/include/php/Zend/zend_modules.h: No such file or directory grep: /usr/local/include/php/Zend/zend_extensions.h: No such file or directory Configuring for: PHP Api Version: Zend Module Api No: Zend Extension Api No: rebuilding aclocal.m4 rebuilding configure rebuilding config.h.in -------------------- The script should show an error message that the file hasn't been found, and show how to use --with-phpize.

What file? 'phpize'?

I used the parameter and got a config script. Running it, I get: --- checking for PHP-GTK support... yes, shared checking for PHP executable in /usr/local/bin... found version 5.1.2 configure: error: PHP CLI version is required, found --- Found what? Maybe the error is due to my setup, because /usr/local/bin/php -> /usr/bin/php /usr/bin/php -> p5 /usr/bin/p5 = shell script which calls /data/cvs/php/php5install/bin/php -c /data/cvs/php/php5install/bin/ $* At least, it works when using --with-php-config=/path/to/php-config The rest is working as expected. I know that the last problem with the "found" can't be solved, but the buildconf should get a hint about what to do

I ran into something like this when I didn't have X server started. After starting it, the configure worked normally. What should buildconf do exactly? We should actually strive for not making users run buildconf when they untar the package. They should just do ./configure (with appropriate parameters) and compile. -Andrei