If you're simply bored to call your script like this:

    perl myscript.pl arg1 arg2 ...
[download]

#!/path/to/perl
[download]

     $ chmod u+x myscript.pl
[download]

If you really want an executable, but just for fun and you can accept some degree of uncertainty about the results, you can use the perlcc compiler, which should generate a C source file from your Perl script. You can peruse perlcc for details, but be sure to read the disclaimer:

       The code generated in this way is not guaranteed to work.
       The whole codegen suite ("perlcc" included) should be con-
       sidered very experimental. Use for production purposes is
       strongly discouraged.
[download]

¹I mean that you must start the given line from the first byte of your script.

It's not very clear for me what you really want or why. I suppose you are on Windows, or you wouldn't have that sort of question/problem. Here are the options i know:

• perl2exe (as others have already mentioned) makes big (1+ MB) executables containing the Perl interpreter along with your script and required modules.
• pl2bat needs Perl installed. It encapsulates your perl script into an executable windows batch file (through the use of a few simple but smart tricks to hide the 2 different languages from each other; have a look at the .bat file).
• map the .pl extension to Perl. Also needs Perl installed. The relevant commands to create the mapping are assoc and ftype. Type help ftype for an example. (I don't recommend this. Depending on what your scripts do, an accidental double-click can do quite some damage).

What I recently did on a small (~ 15 people) network is to put Perl and various little utilities on the server, and added this to the logon script:

setx PERLBIN \\Serv\apps\Perl\bin
setx PERL5LIB \\Serv\apps\Perl\lib:\\Serv\apps\Perl\site\lib
setx BIN \\Serv\apps\bin
setx PATH %PERLBIN%;%BIN%

setx can be found somewhere on the Microsoft site. It's from some resource kit.

There are several perfectly valid reason he would want to do this. I will give the one that has come up more than once:

Not all software is developed for in house use, which can lead to following problems:

1. Many people (clients) don't understand the concept of an interpreter (Why can't I just click on it? What is that black DOS window that pops up, etc)
2. Deploying the Perl interpreter on many machines could become a large task.
3. Even if they have Perl installed, you have to be sure they have all the modues you need (Tk, LWP etc)
4. It is ever so much easier to deliver 1 executable file, rather than a host of supporting modules as well as the whole Perl interpeter.

in support of what scmason mention's. If you package the new exe up as an MSI file (microsoft Installer) you can distribute it through active directory which makes life a lot easier for a poor busy admin :-) I use activestates "perlmsi" to create these packages and then distribute them to appropriate OU's (organisational Unit).