error installing Perl6

[Richard Hainsworth]

Just got error from new clone rakudo directory, Viz.

richard@jupiter:~/Development$ git clone git://github.com/rakudo/rakudo.git
Initialized empty Git repository in /home/richard/Development/rakudo/.git/
remote: Counting objects: 22035, done.
remote: Compressing objects: 100% (5908/5908), done.
remote: Total 22035 (delta 16176), reused 21484 (delta 15720)
Receiving objects: 100% (22035/22035), 2.92 MiB | 925 KiB/s, done.
Resolving deltas: 100% (16176/16176), done.
richard@jupiter:~/Development$ cd rakudo/
richard@jupiter:~/Development/rakudo$ perl Configure.pl --gen-parrot
Generating Parrot ...
/usr/bin/perl build/gen_parrot.pl
--prefix=/home/richard/Development/rakudo/parrot_install --optimize

Checking out Parrot r42403 via svn...
Can't exec "svn": No such file or directory at build/gen_parrot.pl line 47.

Configuring Parrot ...
/usr/bin/perl Configure.pl
--prefix=/home/richard/Development/rakudo/parrot_install --optimize
Unknown option: prefix
Unknown option: optimize
===SORRY!===
Unable to locate parrot_config

To automatically checkout (svn) and build a copy of parrot r42403,
try re-running Configure.pl with the '--gen-parrot' option.
Or, use the '--parrot-config' option to explicitly specify
the location of parrot_config to be used to build Rakudo Perl.

Building Parrot ...
===SORRY!===
Unable to locate parrot_config

To automatically checkout (svn) and build a copy of parrot r42403,
try re-running Configure.pl with the '--gen-parrot' option.
Or, use the '--parrot-config' option to explicitly specify
the location of parrot_config to be used to build Rakudo Perl.

[Matthew Walton]

On Thu, Nov 12, 2009 at 2:30 PM, Richard Hainsworth
<ric...@rusrating.ru> wrote:

> Can't exec "svn": No such file or directory at build/gen_parrot.pl line 47.

You need to install Subversion in order to allow the build script to
obtain Parrot.

[cma...@gmail.com]

Matthew (>), Richard (>>):

That said, perhaps one could fail earlier in the build script when
something like this occurs.

This whole thread probably belongs on perl6-compiler, not on perl6-language.

// Carl

[Darren Duncan]

I think that a best practice these days is to download and build Parrot
separately (which can be in a custom location) and then separately download and
configure Rakudo to use Parrot's location, rather than use gen_parrot. Parrot
is gotten with Subversion, and Rakudo with Git. I could be wrong. -- Darren Duncan

[Patrick R. Michaud]

On Thu, Nov 12, 2009 at 12:49:01PM -0800, Darren Duncan wrote:
> I think that a best practice these days is to download and build Parrot
> separately (which can be in a custom location) and then separately
> download and configure Rakudo to use Parrot's location, rather than use
> gen_parrot. Parrot is gotten with Subversion, and Rakudo with Git. I
> could be wrong. -- Darren Duncan

It's still often hard to know *which* revision of Parrot to get --
Rakudo doesn't always build against Parrot HEAD. (Phrased differently,
sometimes Parrot introduces a change that breaks Rakudo until we
have a chance to catch up.)

So, for people whose primary aim is to build Rakudo, we continue
to recommend the --gen-parrot approach. That gives the best
shot at getting something working.

If the primary aim is to build and install Rakudo for a more
"site wide" purpose, then installing Parrot first and building
Rakudo to use that makes more sense. But one has to be careful
to match the Rakudo version with the corresponding Parrot version
(in build/PARROT_REVISION of the Rakudo repository).

Pm