From: Timothy Madden <terminatorul@gmail.com>
To: cygwin@cygwin.com
Subject: Pass windows-style paths to the interpreter from the shebang line ?
Date: Wed, 09 Nov 2011 13:40:00 -0000 [thread overview]
Message-ID: <j9dvqh$u92$1@dough.gmane.org> (raw)
Hello
I would like to write a php script to run from my cygwin command line.
I have the php CLI executable (php.exe) in PATH and I use
#!/bin/env php
as the first line of the .php script, and make it executable.
The problem is that bash will than invoke the Win32 native php.exe
binary with the Cygwin-style path of my script as the argument,
and then php complains that it:
`Could not open input file: /home/Adrian/usr/local/bin/parseLog.php´
Which is normal for php.exe, as it does not understand cygwin paths.
I found no way around this problem. I would type `php /scriptname/´
myself but then the script name would no longer be searched on PATH and
I would have to type
'D:\Local\cygwin\home\Adrian\usr\local\bin\parseLog.php' as the script
name at all times.
Is there a way around this ? Can cygwin detect the executable is not a
cygwin application add pass in the right path name ?
Thank you,
Timothy Madden
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2011-11-09 13:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 13:40 Timothy Madden [this message]
2011-11-09 15:30 ` Corinna Vinschen
2011-11-09 15:46 ` Jeremy Bopp
2011-11-09 15:51 ` Corinna Vinschen
2011-11-10 1:14 ` PHP (was: Re: Pass windows-style paths to the interpreter from the shebang line ?) Yaakov (Cygwin/X)
2011-11-10 10:05 ` Corinna Vinschen
2011-11-09 21:16 ` Pass windows-style paths to the interpreter from the shebang line ? Timothy Madden
2011-11-09 21:20 ` Christopher Faylor
2011-11-09 15:51 ` Jeremy Bopp
2011-11-10 1:35 ` Andrey Repin
2011-11-09 16:27 ` Andrew DeFaria
2011-11-09 15:51 ` Marco Atzeri
2011-11-10 1:35 ` Andrey Repin
2011-11-10 9:46 ` Linda Walsh
2011-11-10 10:43 ` Timothy Madden
2011-11-10 14:20 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='j9dvqh$u92$1@dough.gmane.org' \
--to=terminatorul@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).