2008/5/10 Wietse Venema <[EMAIL PROTECTED]>: > Steph Fox: >> Hi Hector, >> >> > I can confirm that nmake v6 from VS C/C++ 6.00 did not exhibit the >> > problem. However nnake (v8) from VS 2005 does exhibit the problem. >> > Richard was using nmake v9 (VS 2008). >> > >> > The problem begins with having /cygwin/bin folder in the PATH statement >> > and RMDIR.EXE found in this folder by nmake (v8, v9). >> >> That would explain why I thought it was something in his setup :) thank you >> for clearing up the mystery. >> >> I committed Richard's changes in 5_3 branch (only, for now) yesterday. >> Wietse may well be correct about the explicit cmd /c being more robust, but >> posted after that commit. > > I am right :-) Plus, Richard improved my suggestion in private email to: > > $(COMSPEC) /c > > This would be robust against changes in future Windows versions > (command.com -> cmd.exe -> whatever). > > Wietse > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
It seems that nmake searches the path for all the shell commands ... echo, del, etc. Using this simple makefile ... all: clean clean: @echo hello world @md bob -rmdir bob /q /s Using my path and pathexts, nmake made 420 searches for echo.xxxx. Adding the $(COMSPEC) /c to all of them seems overkill, but it does remove the issue of having cygwin tools in the path. -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!" -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
