Skip to content
Find file
Fetching contributors…
Cannot retrieve contributors at this time
150 lines (99 sloc) 4.65 KB
This is Parrot, version 0.4.13
Parrot is Copyright (C) 2001-2007, The Perl Foundation.
This code 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.
You need a C compiler, a linker and a make program of course. If you will be
linking with the ICU library you have to download and install it before
configuring Parrot.
Get it from
You also need Perl 5.8.0 or newer to run various configure and build scripts.
For most of the platforms that we are supporting initially, Parrot should build
out of the box. The list of targeted platforms can be found in PLATFORMS.
The current configure system is primitive, as it's only
a temporary solution. It will be happy with most any answers
you decide to feed it. Garbage In, Garbage Out.
For now, unpack your Parrot tarball, (if you're reading this, you've
probably already done that) and type
to run the Configure script. The script extracts
configuration from the running perl5 program. Unfortunately, the perl5
configuration is not set up to compile and link c++ programs, so you
may need to explicitly tell which compiler and linker to
use. For example, to compile C files with 'cc', C++ files with
'CC', and link everything together with 'CC', you would type
perl --cc=cc --cxx=CC --link=CC --ld=CC
See "perl --help" for more options.
For systems like HPUX that don't have inet_pton please run
perl --define=inet_aton
Running will generate a config.h header, a Parrot::Config
module, platform files and some Makefiles.
The file "myconfig" has an overview of configure settings.
Next, run make:
For UNIX like systems that come with its own make, 'gmake' should be
used. (On most Linux systems, this is the default make.)
On windows systems, 'nmake' is used
On other systems, just try 'make'
NOTE: do *NOT* use the '-j' option to make. The dependencies in the generated
Makefile work if you do them sequentially, but running with -j will almost
certainly cause a build error. Patches welcome.
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).
NOTE: If you have trouble linking parrot, this *may* be due to a pre-existing
parrot version installed via 'make install'. Until this issue is resolved,
you may have to delete the installed version of parrot before building a new
one. Our apologies.
You can test parrot by running
make test (or nmake test or gmake test)
You can run the full test suite with
make fulltest
Note: PLATFORMS contains notes about whether test failures are expected
on your system.
On some systems you can install parrot:
make install
This installs a bunch of files in /usr/local. The parrot executable is in
/usr/local/bin. Please note that this feature is currently experimental.
If you want to install Parrot into a non-standard location use:
perl --prefix=/Users/foo/parrot-0.4.12
make install
But please note that dynamic libs will not be found for non-standard
locations unless you set LD_LIBRARY_PATH or similar.
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
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 (--cgoto=0) to disable the computed-goto
core, at a slight cost in runtime speed.
For documentation on the user-visible changes between this version and
previous versions, please see NEWS.
The mailing list for parrot is parrot-porters. Subscribe by sending mail to It is archived at
and available via NNTP at nntp://
You can also read the list via Google Groups at
The following web sites have all the Parrot information you need:
Have fun,
The Parrot Team.
Something went wrong with that request. Please try again.