PHP 4.0 Bug #7078 Updated: esyscmd() in configure.in doesn't get evaluated

ID: 7078 Updated by: sniper Reported By: alex@unixdot.com Status: Closed Bug Type: *Install and Config Assigned To: Comments: Please check this url: http://www.monkey.org/openbsd/archive/ports/ 0007/msg00187.html As it states, there isn't anything wrong in PHP but within your tools. --Jani Previous Comments: --------------------------------------------------------------------------- [2000-10-07 10:11:06] alex@unixdot.com When I use PHP 4.0.2 or the PHP CVS development version and try to create a new configure script using ./buildconf, configure.in doesn't get parsed correctly. esyscmd(./scripts/config-stubs sapi) esyscmd(./scripts/config-stubs ext) both these commands are put literally into the configure script. running ./configure thereafter fails. I double checked the version numbers of the required tools such as automake and they meet the set requirements. when I run manually the command ./scripts/config-stubs sapi and ./scripts/config-stubs ext and paste the output in the place of the esyscmd() in configure.in, ./buildconf generates a correct configure and ./configure configures PHP properly. I hope I have provided you with enough information, but please don't hesitate if more is required (-: --------------------------------------------------------------------------- Full Bug description available at: http://bugs.php.net/?id=7078