Re: PHP 4.0 Bug #6736 Updated: phpize not built until 'make install' is run

On 28 Nov 2000, sniper wrote: > ID: 6736 > Updated by: sniper > Reported By: vorlon@netexpress.net > Status: Closed > Bug Type: *Install and Config > Assigned To: > Comments: > You can always do this in /pear/: > make phpize Oh sure, someone /fixes/ it when I'm not looking... :) FWIW, this did not work in 4.0.1pl2, because there were no targets for 'phpize' and 'php-config'. I'm glad to see it works now. :) Steve Langasek postmodern programmer > Previous Comments: > --------------------------------------------------------------------------- > [2000-09-13 12:10:01] vorlon@netexpress.net > I've noticed what is for me a problem in the way phpize is built: the phpize > script isn't built until install time, which means that when different > options are used for 'make all' and 'make install', it receives the ones > used for 'make install'. Although this helps ensure that the path encoded > into phpize is the path where PHP will really be installed, it makes things > more difficult for binary package managers who want to build complete > packages for PHP without installing it on the local system. Is a compromise > possible here, or will package maintainers who want to include pear need to > duplicate the work of pear/Makefile themselves?