For UNIX like systems that come with its own make, gmake should be used

On windows systems, nmake is used

On other systems, just try make

Now, the interpreter should build. If you are building the ICU library (this is the default on most systems), you need to use GNU make instead (or something compatible with it).

You can test parrot by running

    make test         (or C<nmake test>/C<gmake test>)

You can run the full test suite with

    make fulltest

On some systems you can install parrot:

    make install

This installs a bunch of files in /usr/local/parrot-$VERSION. The parrot executable is in /usr/local/parrot-$VERSION/bin. Please note that this feature is currently experimental. You have to link or copy the executable somewhere into your path. Finally no dynamic extensions from runtime/parrot/dynext are installed, albeit dynamic extensions are searched for in the installed directory structure.

Look at docs/parrot.pod and docs/intro.pod for where to go from here. If you have any problems, see the section "Reporting Problems" in docs/intro.pod. These documents are in POD format. You can view these files with:

    perldoc -F docs/intro.pod

NOTES -----

On some older computers with little RAM, the computed-goto dispatch core (ops/core_ops_cg.c) may take a while to compile or may fail to compile at all. You can pass a flag to Configure.pl (--cgoto=0) to disable the computed-goto core, at a slight cost in runtime speed.

CHANGES -------

For documentation on the user-visible changes between this version and previous versions, please see NEWS. The full changelog is (or should be) available as ChangeLog.

MAILING LISTS -------------

The mailing list for parrot is perl6-internals. Subscribe by sending mail to perl6-internals-subscribe@perl.org. It is archived at http://nntp.perl.org/group/perl.perl6.internals

WEB SITES ---------

The following web sites have all the Parrot information you need: http://dev.perl.org/ http://cvs.perl.org/ http://www.parrotcode.org/

Have fun, The Parrot team.