At 11:47 PM 3/19/2001 +0000, Hamish Lawson wrote:
> > In order not to have change the "#!/usr/bin/env python" line in
> > scripts, I had made a directory c:\usr\bin and put in there a copy of
> > env.exe from the djgpp toolset (gcc and UNIX tools for Windows).
> > Though this invocation works from the command line, it seems to hang
> > when invoked from Apache. I replaced it with the version of env.exe
> > from Cygwin (another UNIX-like toolset for Windows) and that worked.
>Chuck Esterbrook wrote:
> > Interesting. Sounds like a tip that could go in the InstallGuide.
> > Frankly, I'm disappointed that Apache for Windows is smart enough to
> > interpret "#!python", but not "#!/usr/bin/env python". That's another
> > one of those cases where I think they should "do the smart thing" and
> > make life easier.
>"#!/usr/bin/env python" *does* work if I use Cygwin's env.exe, just not
>djgpp's env.exe. I hadn't immediately thought of the latter as being
>the source of my hanging WebKit.cgi problem, as I'm sure I've used it
>in a "#!/usr/bin/env" line for other scripts in the past; I've
>certainly been able to use a similar trick with "#!/usr/bin/python"
Yeah, I know it works if you get djgpp or cygwin, but when I first got
Apache, I didn't have or want either. My point is that "/usr/bin/env foo"
exists only for the purpose of finding something in the search path, a
capability that Apache already has. They could have special cased the
situation where /usr/bin/env wasn't present on disk by pretending it wasn't
present in the file.