in reply to Re: Issues with pp and Tk
in thread Issues with pp and Tk

If running multiple versions of perl you should run pp for the version of perl you're actually using. Otherwise, madness lies ahead. Binary comparability, version differences...

I'd no idea anyone used ActiveState on MacOS. If you have the time consider looking at a combination of perlbrew and cpanm for perl & module installs.

Replies are listed 'Best First'.
Re^3: Issues with pp and Tk
by Chuma (Scribe) on Oct 19, 2017 at 11:04 UTC

    I should indeed, if I knew how to do that.

    I also used to think ActivePerl was just for Windows. I tried for months getting "normal" Perl to work properly, digging my way through endless indecipherable Unix errors, until I finally found that you could just install ActivePerl and have things at least sort of work. There may be better options, but I'm a simple Mac user, I don't get that complicated stuff. I just want to click an app, if possible.

[reply]

      "I also used to think ActivePerl was just for Windows."

      I've never believed this to be the case. FWIW using Strawberry Perl removes all of the headaches of working on Windows by giving you a sensible build environment, which ActiveState does not. As mentioned perlbrew will set everything up for you in an sane manner.

      "I should indeed, if I knew how to do that."

      Since you've used ActiveState it'll be where ever the ppd file installed it to. Either set a sane environment variable (previously) so that the path to the version of perl you want to use has precedence, or just call pp with the full path, for example something like /Wherever/You/Installed/ActiveState/bin/pp. You can't call pp for the system perl and expect it to work with other versions of perl that you have installed.

[reply]
[d/l]
[select]
        It's installed in /usr/local in my case, but there's no pp in the bin folder. There's plenty of other stuff, but nothing I recognise as useful.
[reply]

In Section Seekers of Perl Wisdom