Your file has a bunch of binary carriage returns in it. Looks like you did not correctly transfer the file from a non-Unix OS to Unix (or vice-versa) in ASCII form. The problem occurs because *with* the -w flag, the carriage return can be safely ignored by Perl, however, without it, your line looks something like this:
#!/usr/bin/perl^M
Since the carriage return has to be treated as if it were a normal ASCII byte, it's looking for the binary perl^M to execute your script, not perl. Thus, you get "not found".

The fix: Transfer the file again correctly, dropping the carriage returns. Alternatively, you can use the search/replace feature in, say, vi, to strip them out: :%s/^V^M//g (where the ^V is a control-V (quote the next character) and the ^M is a control-M), or use something similar in a Perl one-liner.


In reply to Re: -w more than a warning? by Fastolfe
in thread -w more than a warning? by jptxs

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.