Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Odd Perl interpreter problem



On Sat, 29 Dec 2001, Ron Peterson wrote:
>On Sat, 29 Dec 2001, Lars Kellogg-Stedman wrote:
>> > I have #!/usr/bin/perl as interpreter line in scripts.
>> > I get "bad interpreter: no such file or directory" messages when trying to
>> > run the script.
>>
>> Make sure there aren't any extra spaces after the #! line.
>> '#!/usr/bin/perl ' is not the same as '#!/usr/bin/perl'.
>
>Similar problem can happen if you edit a perl script on a samba share
>using notepad.  You'll end up with carriage-return linefeed, rather than
>just a newline.

I do `od -c script.pl` to see exactly the file contents.
Sometimes there could be a ^M before the shebang line or
some other "invisible" characters.
Also make sure you spelled /usr/bin/perl correctly. :)





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org