in reply to Help with pp - Perl Packer

Did you run the exe on the same system you use to create it? The reason I ask is that this (: is not an identifier) looks like a problem I'd expect to see from a shell/environment issue, rather than perl. Without knowing more about the code you are packaging I'm having a hard time thinking about what could cause this.

As a side note I'd suggest running pp with the -x option to run your code and check for additional run time dependencies. You can unpack the 'executable' you've created (just unzip it somewhere) and see exactly what has been packaged.

Replies are listed 'Best First'.
Re^2: Help with pp - Perl Packer
by perloHolic() (Beadle) on Jan 29, 2015 at 16:32 UTC

    Thanks for the swift response. when you say shell/environment issue, is that when running the executable or creating it? the systems are the same as far as I am aware. I would happily post the code up, although it is rather large, and editing it to make it not work specific/anonomous may take longer than it did to write the thing i'm afraid.

    Is the fact the executable does run without error highlight that perhaps the perl is ok, and as you say more of a systems issue? one thing I did try in order to eliminate some possibilites is to create a .exe to run as an icon from a windows environment but i'm guessing i'm getting way ahead of myself there as this didn't get close to even working....?

[reply]

      I mean the environment running the executable you created which results in the error. Are you working with environment variables within the code? Posting a short example which recreates the issue would be advantageous.

      "Is the fact the executable does run without error highlight that perhaps the perl is ok, and as you say more of a systems issue?"

      This statement has confused me. I thought your report was that the executable did spit out an error at the prompt?

      "one thing I did try in order to eliminate some possibilites is to create a .exe to run as an icon from a windows environment"

      I think your efforts would be better spent isolating the problem in the current environment.

[reply]

        My apologies for the confusion. I simply meant that running the perl script independantly works fine. Running the executable also 'works' but displays in an undesirable way due the the : not an identifier message.

        FOR EXAMPLE: when I run my program it clears the gui window down, and displays username and password in the centre in order for the user to input details. - However when running the executable, the screen is cleared, but the user name is right at the bottom of the screen, with the :not an identifier just above it, and the same stands for when the user has input correct details, the main menu is all messed up because the : not an identifier is printed to screen and shifts everything down.

        Its almost like 'something' is getting stored in some kind of buffer. Hopefully i explain this bit right - I changed the executable name and now the last letter on the command line is before the error like: e: is not and identifier, which is almost like it's being left behind asfter pressing 'return' to run the script - does that sound plausable?

[reply]

In Section Seekers of Perl Wisdom