This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: bash bad interpreter - a new twist!


On Thu, Mar 25, 2004 at 11:02:24PM -0600, Tom Rodman wrote:
>>I'm using cygwin (september 2003 build) and ActiveState perl.  To connect 
>>ActiveState into cygwin I use a proxy /usr/local/bin/perl bourne shell 
>>script that essentially transalates the paths (cygpath -w) and delegates to 
>>the ActiveState perl.exe binary.  Given the following foobar script:
>>
>>#!/usr/local/bin/perl -w
>>print "foobar world\n";
>
>The "#!" construct must always refer to a binary, never to another
>script (to avoid loops?).  I ran into the same issue.  The UNIX
>standard is what I just said, but earlier (and current?) cygwin
>versions (wrongly) sorta supported a script.  In 1.3.20 it works about
>2 out of 5 times or so - if you try a similar approach on a UNIX box it
>will fail *every* time.

Actually, no.  It won't.  The #! can refer to a script.  Just tried it
on Tru64 and on linux.

The second script would have to be carefully constructed to recognize
the 'print "foobar world\n"', though.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]