Description:
------------
Running "buildconf" or "configure" on Windows runs a batch file, whose only purpose is to call cscript in order to run a .js file that contins the actual configure scripts.

By default, the file association for .js is set up in such a way that cscript can tell which script engine (jscript) to use without further instruction. However, if the file association has been changed from the default (imagine an IDE has been set up that can edit .js files) then cscript will fail to execute the script.

The solution is to put an explicit "/e:jscript" flag in all calls to cscript, which will ensure that the script will always be executed successfully.

I have a pull request that implements this change:

https://github.com/php/php-src/pull/5101

Test script:
---------------
buildconf

Expected result:
----------------
Rebuilding configure.js
Now run 'configure --help'

Actual result:
--------------
Input Error: There is no script engine for file extension ".js".