Parrot VM fork for my own work. !! Branches may rebase !!
Fetching latest commit…
Cannot retrieve the latest commit at this time
This is Parrot, version 0.6.4 ------------------------------ Parrot is Copyright (C) 2001-2008, The Perl Foundation. $Id$ LICENSE INFORMATION ------------------- 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. PREREQUISITES ------------- 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 http://www-306.ibm.com/software/globalization/icu/downloads.jsp 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. INSTRUCTIONS ------------ For now, unpack your Parrot tarball, (if you're reading this, you've probably already done that) and type perl Configure.pl to run the Configure script. The Configure.pl 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 Configure.pl 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 Configure.pl --cc=cc --cxx=CC --link=CC --ld=CC See "perl Configure.pl --help" for more options and docs/configuration.pod for more details. For systems like HPUX that don't have inet_pton please run perl Configure.pl --define=inet_aton Running Configure.pl will generate a config.h header, a Parrot::Config module, platform files and many 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' 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 Configure.pl --prefix=/Users/foo/parrot-0.6.4 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 "How To Submit A Bug Report" in docs/submissions.pod. These documents are in POD format. You can view these files with the command: 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. MAILING LISTS ------------- The mailing list for parrot is parrot-porters. Subscribe by sending mail to email@example.com. It is archived at http://www.nntp.perl.org/group/perl.perl6.internals and available via NNTP at nntp://nntp.perl.org/perl.perl6.internals You can also read the list via Google Groups at http://groups-beta.google.com/group/perl.perl6.internals FEEDBACK, PATCHES, etc. _______________________ See F<docs/submissions.pod> for more information on reporting bugs and submitting patches. WEB SITES --------- The following web sites have all the Parrot information you need: http://www.parrotcode.org/ http://www.perlfoundation.org/parrot/ http://dev.perl.org/perl6/ http://bugs6.perl.org/perl6/ http://pugscode.org/ Have fun, The Parrot Team.