On Fri, May 21, 2010 at 17:15, Peter Kjellerstedt
<peter.kjellerstedt@xxxxxxxx> wrote:
> This does not work. You cannot give arguments to an application
> started via /usr/bin/env; it will interprete everything after
> /usr/bin/env as the application name and fail with:
>
> /usr/bin/env: perl -w: No such file or directory
Yep. It would have to be changed to
/usr/bin/env perl
and add
BEGIN {$^W = 1;}
to the script.
That been said, I've used /usr/bin/env perl for customer applications
for years and years, without problems. Things wouldn't have worked
otherwise, because on e.g. IRIX systems the /usr/bin/perl version
would be 5.005 and the /usr/freeware version would be 5.6.1.BUt the
caveat is that you'll need to change -w to the above.
-Tor
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html