I am stumped.. I have a script for which I have verified perl is indeed where it should be, but if you execute it like this:

./script.pl

it gives the message

: bad interpreter: No such file or directory

IF you go into the script and change

#!/usr/bin/perl
to
#!/usr/bin/perl -w

It executes.. but there are SO many errors, it doesn't work (it's a CGI script from somebody, that has "issues").

Has anyone ever seen this?? It has some "require" statements for some other perl chunks, and I was wondering if that had anything to do with it, but I edited a few scripts, and it doesn't seem to affect anything.

The script lives on a local file system, and has proper permissions.

Thanks a lot ahead of time.

Update:

I did not see any control chars, but ran dos2unix anyway on it, and then it started working. Really strange.

Thanks everyone!!

In reply to bad interpreter: No such file or directory by carric

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.