Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Rakudo Perl -- Perl 6 on Parrot

This branch is 965 commits ahead and 55 commits behind master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Rakudo Perl 6
    This is Rakudo Perl, a Perl 6 compiler for the Parrot virtual machine.

    Rakudo Perl is Copyright (C) 2008-2011, The Perl Foundation. Rakudo Perl
    is distributed under the terms of the Artistic License 2.0. For more
    details, see the full text of the license in the file LICENSE.

    This directory contains only the Rakudo Perl 6 compiler itself; it 
    does not contain any of the modules, documentation, or other items
    that would normally come with a full Perl 6 distribution.  If you're
    after more than just the bare compiler, please download the latest
    Rakudo Star package from .

  Build requirements (Installing from source)
    For building Rakudo you need at least a C compiler, a "make" utility,
    and Perl 5.8 or newer. To automatically obtain and build Parrot you
    may also need a a git client, which is also needed for fetching the
    test suite.

    In order to fully support Unicode, you'll also want to have the ICU
    library installed (<>). Rakudo can run
    without ICU, but some Unicode-related features do not work properly.

    As an example, on Debian GNU/Linux or Ubuntu Linux, the necessary
    components for building Rakudo can be installed via the command

        aptitude install build-essential libicu-dev git-core

    (Perl is installed by default already). To enable parallel testing you
    also need the CPAN module Test::Harness in version 3.16 or newer; you
    can control the number of parallel jobs with the "TEST_JOBS" environment

  Building and invoking Rakudo
    Because Rakudo is under rapid development, we generally recommend
    downloading Rakudo directly from github and building from there:

        $ git clone git://

    If you don't have git installed, you can get a tarball or zip of Rakudo
    from <>. Then unpack the
    tarball or zip.

    If you already have cloned Rakudo from github, you can get (pull) the
    most recent version from github like this:

        $ cd rakudo
        $ git pull

    Once you have an up-to-date copy of Rakudo, build it as follows:

        $ cd rakudo
        $ perl --gen-parrot
        $ make

    This will create a "perl6" or "perl6.exe" executable in the current
    (rakudo) directory. Note that if you have multiple (Perl 5) "perl"s in
    your path, you may need to use a fully qualified path to the appropriate
    executable (or update your PATH environment variable).

    Programs can then be run from the build directory using a command like:

        $ ./perl6

    Important: To run Rakudo from outside the build directory, you must run

        $ make install

    This will install the "perl6" (or "perl6.exe" binary on windows) into
    the "install/bin" directory locally, no additional root
    privileges necessary.

    The "--gen-parrot" above option tells to automatically
    download and build the most appropriate version of NQP and Parrot 
    into local "nqp/" and "parrot/" subdirectories, install NQP and Parrot
    into the "install/" subdirectory, and use them for building Rakudo.
    It's okay to use the "--gen-parrot" option on later invocations of; the configure system will re-build NQP and/or Parrot 
    only if a newer version is needed for whatever version of Rakudo 
    you're working with.

    If you already have Parrot installed, you can use 
    "--with-parrot=/path/to/bin/parrot" to use it instead of
    building a new one.  This installed Parrot must include its
    development environment.  Similarly, if you already have NQP
    installed, you can specify "--with-nqp=/path/to/bin/nqp"
    to use it.  (Note that this must be NQP, not the NQP-rx that
    comes with Parrot.)

    The versions of any already installed NQP or Parrot binaries must
    satify a minimum specified by the Rakudo being built --
    and "make" will verify this for you.  Released versions of Rakudo
    always build against the latest release of Parrot; checkouts of 
    the HEAD revision from github often require a version of Parrot 
    that is newer than the most recent Parrot monthly release.

    Once built, Rakudo's "make install" target will install Rakudo and its
    libraries into the directories specified by the Parrot installation
    used to create it.  Until this step is performed, the "perl6" 
    executable created by "make" above can only be reliably run from 
    the root of Rakudo's build directory.  After "make install" is 
    performed, the installed executable can be run from any directory 
    (as long as the Parrot installation that was used to create it 
    remains intact).

    If the Rakudo compiler is invoked without an explicit script to run, it
    enters a small interactive mode that allows Perl 6 statements to be
    executed from the command line.

    See the manual page ("docs/running.pod") for more about command-line

   Build/install problems
    Occasionally, there may be problems when building/installing Rakudo.
    Make sure you have a backup of any custom changes you have done to the
    source tree before performing the following steps:

    Try to remove the "install/" subdirectory:

        $ cd rakudo
        $ rm -r install
        $ git pull
        $ perl --gen-parrot
        $ make

    Or, in case you are really stuck, start with a fresh source tree:

        $ rm -r rakudo
        $ git clone git://

  Running the test suite
    Entering "make test" will run a small test suite that comes bundled with
    Rakudo. This is a simple suite of tests, designed to make sure that the
    Rakudo compiler is basically working and that it's capable of running a
    simple test harness.

    Running "make spectest" will import the official Perl 6 test suite from
    the "roast" repository <> and run all
    of these tests that are currently known to pass.

    If you want to automatically submit the results of your spectest run to
    a central server, use "make spectest_smolder" instead. You need the
    Perl 5 module TAP::Harness::Archive and an active internet connection
    for that. The smoke results are collected at

    At present we do not have any plans to directly store the official test
    suite as part of the Rakudo repository, but will continue to fetch it 
    from the roast repository.  Releases of Rakudo get a snapshot of
    the roast repository as of the time of the release.

    You can also use "make" to run an individual test from the command line:

        $ make t/spec/S29-str/ucfirst.t
        t/spec/S29-str/ucfirst.rakudo ..
        ok 1 - simple
        ok 2 - empty string
        ok 3 - # SKIP unicode
        ok 4 - # SKIP unicode
        # FUDGED!
        All tests successful.
        Files=1, Tests=4,  1 wallclock secs ( 0.02 usr  0.00 sys +  0.57 cusr  0.06 csys =  0.65 CPU)
        Result: PASS

    If you want to run the tests in parallel, you need to install a fairly
    recent version of the Perl 5 module Test::Harness (3.16 works for sure).

  Where to get help or answers to questions
    There are several mailing lists, IRC channels, and wikis available with
    help for Perl 6 and Rakudo on Parrot. Figuring out the right one to use
    is often the biggest battle. Here are some rough guidelines:

    The central hub for Perl 6 information is .
    This is always a good starting point.

    If you have a question about Perl 6 syntax or the right way to approach
    a problem using Perl 6, you probably want the ""
    mailing list or the "" channel.  The perl6-users
    list is primarily for the people who want to use Perl 6 to write
    programs, so newbie questions are welcomed there.  Newbie questions
    are also welcome on the #perl6 channel; the Rakudo and Perl 6
    development teams tend to hang out there and are generally glad 
    to help.  You can follow "@rakudoperl" on Twitter, and there's
    a Perl 6 news aggregator at <> .

    Questions about NQP can also be posted to the #perl6 IRC channel.
    For questions about Parrot, see <> for links and
    resources, or join the #parrot IRC channel on .

  Reporting bugs
    Bug reports should be sent to "" with the moniker
    [BUG] (including the brackets) at the start of the subject so that it
    gets appropriately tagged in the RT system (
    Please include or attach any sample source code that exhibits the bug,
    and include either the release name/date or the git commit identifier.
    You find that information in the output from "perl6 --version" (or in
    the first line of "git log", if Rakudo fails to build). There's no need
    to cc: the perl6-compiler mailing list, as the RT system will handle
    this on its own.

  Submitting patches
    If you have a patch that fixes a bug or adds a new feature, please
    submit it to "" with the moniker [PATCH] (including
    the brackets) at the start of the subject line. We'll generally accept
    patches in any form if we can get them to work, but unified diff from
    the "git" command is greatly preferred. In general this means that in
    the "rakudo" directory you make your changes, and then type

        git commit -m 'Your commit message' changed/
        git format-patch HEAD^

    This will generate a file called "001-your-commit-message.patch", or
    more of them if you made multiple commits; please attach these to your

    (Note to the maintainers: you can apply these patches with the 
    "git-am -s" command; it preserves meta information like author).

  How the compiler works
    See docs/compiler_overview.pod.

    Patrick Michaud "" is the current pumpking for
    Rakudo Perl 6.  See CREDITS for the many people that have contributed
    to the development of the Rakudo compiler.
Something went wrong with that request. Please try again.