[SOLVED] Perl: cannot use: "use v5.14"

gregAstley · 08-11-2013, 11:10 AM

I have just upgraded my version of perl to 5.18 in an attempt to try and fix this one but it didn't work. Essentially, the following "program"

#!/usr/bin/perl
use v5.14;

fails to run with the error:

Perl v5.14.0 required--this is only v5.12.4, stopped at ./Perl line 2.
BEGIN failed--compilation aborted at ./Perl line 2.

I have tried copy pasting sections of the error string into google and though I get a few hits I have found nothing that can help me with this one...anybody got any ideas?

NevemTeve · 08-11-2013, 01:42 PM

Either your Perl is lying, or it is really version 5.12.4

Code:

perl -v
which perl
dpkg -l perl

gregAstley · 08-11-2013, 01:59 PM

Quote:

Originally Posted by NevemTeve

Either your Perl is lying, or it is really version 5.12.4

Code:

perl -v
which perl
dpkg -l perl

Firstly, thatnks for the response, and secondly, wow...this is wierd, firstly, the new installation seems to have had no effect (configure, make, make install seemed to work), and finally, my output from those commands is as follows:

Code:

greg@greg-Aspire-5742:~$ perl -v

This is perl 5, version 14, subversion 0 (v5.14.0) built for i686-linux

Copyright 1987-2011, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

greg@greg-Aspire-5742:~$ which perl
/home/greg/perl5/perlbrew/perls/perl-5.14.0/bin/perl
greg@greg-Aspire-5742:~$ dpkg -l perl
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  perl           5.12.4-4ubuntu Larry Wall's Practical Extraction and Report
greg@greg-Aspire-5742:~$

this can't be healthy :/

chrism01 · 08-11-2013, 11:16 PM

You're pointing at 2 different installs

Code:

/usr/bin/perl    # evidently perl 5.12

perl     # evidently 5.14 in path /home/greg/perl5/perlbrew/perls/perl-5.14.0/bin/perl

Just change the path at the top of the perl program OR put a symlink there to point at the 5.14 OR insert the 5.14 path in $PATH before /usr/bin.

gregAstley · 08-12-2013, 02:00 PM

Quote:

Originally Posted by chrism01

You're pointing at 2 different installs

Code:

/usr/bin/perl    # evidently perl 5.12

perl     # evidently 5.14 in path /home/greg/perl5/perlbrew/perls/perl-5.14.0/bin/perl

Just change the path at the top of the perl program OR put a symlink there to point at the 5.14 OR insert the 5.14 path in $PATH before /usr/bin.

I opted for the symlink option (I was tempted to nuke the 5.12, 5.14, and recently (though ineffectually) the install of 5.18 but was worried I might break something in the process)

It all works - thanks for that :]

NevemTeve · 08-12-2013, 02:39 PM

Usually, locally compiled programs go into /usr/local (./configure --prefix=/usr/local), and script-headers often points there, too:

Code:

#!/usr/local/bin/php
...

But, if you don't have locally compiled PHP, you are to create a symlink: ln -s /usr/bin/php /usr/local/bin/php

gregAstley · 08-12-2013, 03:10 PM

Quote:

Originally Posted by NevemTeve

Usually, locally compiled programs go into /usr/local (./configure --prefix=/usr/local), and script-headers often points there, too:

Code:

#/usr/local/bin/php
...

But, if you don't have locally compiled PHP, you are to create a symlink: ln -s /usr/bin/php /usr/local/bin/php

Thanks, for what its worth, I did have a look at what is inside my /usr/local directory and with the exception of some xml related binaries there is nothing useful in there for me. As per my response to chrism01 above however, all is now well again :]

NevemTeve · 08-12-2013, 11:19 PM

Certainly, as you've compiled your perl with configure-option --prefix=/home/greg/perl5/perlbrew/perls/perl-5.14.0
That's okay if you are only experimenting; but if you actually want to use it, --prefix=/usr/local is a better idea.