in reply to making perl executable

You could make life a lot easier for yourself if you stop ignoring the advice you've been given. Your previous threads on this topic are all over the place. Had you actually read the documentation for pp you'd know that using the -P option isn't what you want to do:

-P
Create stand-alone perl script; do not package to a standalone binary.

[download]

Please stop doing things at random in the hope they'll do what they want.

Update: fixed typo.

Replies are listed 'Best First'.
Re^2: making perl executable
by Anonymous Monk on Jul 05, 2013 at 14:06 UTC
    i know that , i made the exe file first , just to be safe i made the pl file . If you could please help with the problem of having cpan , in the exe that would be much more helpful than pointing my mistakes
[reply]

      "i know that ,"

      Actually, you don't seem to know what you think you do.

      "just to be safe i made the pl file ."

      Since you want to use pp to create an executable, safety has nothing to do with the requirement to have some perl code. Where in any of the previous discussions we've had, or the documentation does it tell you to attempt what you're trying to do? You must provide perl code as an input to pp, otherwise what do you think you're going to package?

      Using pp you want to create a stand alone executable containing all the modules your code uses. At no point do you want to include cpan here. The second example in the documentation shows you how to create a standalone executable.

      pp -o hello hello.pl      # Pack 'hello.pl' into executable 'hello'
                          # (or 'hello.exe' on Win32)

      [download]
[reply]
[d/l]
        I gave the perl script as an input to the pp like pp -o hello hello.pl but it creates only a read only file not executable
[reply]
[d/l]

In Section Seekers of Perl Wisdom