http://qs321.pair.com?node_id=1097824


in reply to How to run perl5.21.3 as "perl"

I don't know exactly what's causing the problem, but a workaround might be to set up a shell alias. Most Unix shells (bash, tcsh, etc) support them, though the syntax to define them varies from shell to shell, so you'd need to check your shell's manual.

toby döt ink

Replies are listed 'Best First'.
Re^2: How to run perl5.21.3 as "perl"
by syphilis (Archbishop) on Aug 18, 2014 at 11:37 UTC
    I was half expecting it might have been something obvious that I was missing.
    Something in your reponse made me suddenly think "hang on ... I'm doing this over an ssh connection". So I decided to see whether the same problem existed when I sat at the computer's terminal (using identical path) and accessed it directly ... and it didn't !! Everyting works as expected when I'm sitting at the terminal.

    But what makes it even weirder is that I have other perls under ~, and those perls *are* accessible as "perl" over the ssh connection.
    For example: 
    sisyphus-sis@debian-sis:~$ echo $PATH
/home/sisyphus-sis/perl520-m64-multi/bin:/usr/local/bin:/usr/bin:/bin:
+/usr/local/games:/usr/games
sisyphus-sis@debian-sis:~$ which perl
/home/sisyphus-sis/perl520-m64-multi/bin/perl
sisyphus-sis@debian-sis:~$ perl -le 'print $^X'
/home/sisyphus-sis/perl520-m64-multi/bin/perl
sisyphus-sis@debian-sis:~$

    [download]
    No problems with that (or any of the 7 other installations of) "perl" over the ssh connection. It's just the bleadperl that won't play ball.
    Thanks for the reply tobyink

    Cheers,
    Rob
[reply]
[d/l]

In Section Seekers of Perl Wisdom