That doesn't really tell us anything. How did it 'fail', what have you tried (options and such, although I know next to none about perlbrew)?idaho-axe said:I tried with 9.1 amd64 to use perlbrew to get perl 5.18 and it failed.
Well, not really "going" because I already use a Perl version which I got from the ports collection, so I have no intention to mess up my system.idaho-axe said:Anyone here have 5.18 perl going?
$ ./perl -v
This is perl 5, version 18, subversion 0 (v5.18.0) built for amd64-freebsd
$ ./configure.gnu && make
to get the results you see up there. It will take a lot more to get this to replace your current Perl version safely.To my knowledge there is no port yet for Perl 5.18. The latest version seems to be lang/perl5.16. As such I grabbed the tarball, but it's also why I would advice to wait for a port to appear.idaho-axe said:interesting, so you did not use the port, but the perl tarball and bsd make? hm
ShelLuser said:Most likely true. As I hinted at; I can easily manage to build this thing to be used within my home directory. But trying to get the rest of my system to use it (Apache, AWStats, Midnight Commander, Spamassassin (very important program for me) or even Webmin (idem)), now that's something else..
Unless you have a specific reason for 5.18 I'd really advice you to stick with the lang/perl5.16 port for the time being. Easier to setup, much easier to maintain.
make test
, make install
? I am running the configure.gnu && make
, and some part of me wonders why GNU on BSD, but ok. make install
because as mentioned above: I didn't really feel like trashing my system, I'm happy with my current version of Perl.# cd /usr/ports/lang/perl5.16
# make install clean