forked from parrot/parrot
/
README
161 lines (114 loc) · 5.18 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
This is Parrot, version 2.10.1
-----------------------------
Parrot is Copyright (C) 2001-2010, Parrot Foundation.
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.
OVERVIEW
--------
Parrot is a virtual machine designed to efficiently compile and execute
bytecode for dynamic languages.
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://site.icu-project.org/download
You also need Perl 5.8.4 or newer, and Storable 2.12 or newer
for running various configure and build scripts.
For most of the platforms that we are supporting initially, Parrot should build
out of the box. docs/parrot.pod lists the core platforms. PLATFORMS provides
reports on the platforms on which Parrot has been built and tested.
HOW TO GET PARROT FROM GITHUB
-----------------------------
Firstly, you should install Git.
Linux:
The method depends on your distribution. To install you should execute (as root or sudo <cmd>):
On Ubuntu/Debian (apt-based):
apt-get install core
On Red Hat, Fedora (rpm-based):
yum install git-core
on Gentoo (portage):
emerge -av dev-vcs/git
Windows:
There are 2 Git ports on Windows:
msysgit (http://code.google.com/p/msysgit/downloads/list)
TortoiseGit (http://code.google.com/p/tortoisegit/downloads/list)
In Git, branches represent some major changes of source and tags represent different releases.
You can view the list of branches and tags at http://github.com/parrot/parrot
To fetch the source from the master branch:
git clone git://github.com/parrot/parrot.git
To fetch the source from a branch:
git clone git://github.com/parrot/parrot.git -b <branch>, e.g:
git clone git://github.com/parrot/parrot.git -b gsoc_threads
To fetch the source from a tag:
git fetch git://github.com/parrot/parrot.git tag <tag>, e.g:
git fetch git://github.com/parrot/parrot.git tag RELEASE_2_10_1
If you fetched the source from a specific branch, you can merge it with the master:
git branch -to list branches, active one will be marked with *
git merge master -to merge active branch with master
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. (Configure.pl will tell you which version of make it
recommends for your system.)
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". You can run the tests in parallel
with "make TEST_JOBS=3 test".
You can run the full test suite with
make fulltest
Note: PLATFORMS contains notes about whether test failures are expected
on your system.
You can install Parrot with:
make install
By default, this installs in /usr/local, with the Parrot executable in
/usr/local/bin. If you want to install Parrot into another location use:
perl Configure.pl --prefix=/home/joe/bird
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
CHANGES
-------
For documentation on the user-visible changes between this version and
previous versions, please see NEWS.
MAILING LISTS
-------------
The Parrot user mailing list is parrot-users@lists.parrot.org. Subscribe by
filling out the form at http://lists.parrot.org/mailman/listinfo/parrot-users .
The list is archived at http://lists.parrot.org/pipermail/parrot-users/ .
For development discussions see the information in docs/gettingstarted.pod.
FEEDBACK, PATCHES, etc.
-----------------------
See docs/submissions.pod for more information on reporting bugs and
submitting patches.
WEB SITES
---------
The following web sites have all the information you need about Parrot:
http://www.parrot.org/
http://trac.parrot.org/
http://docs.parrot.org/
Have fun,
The Parrot Team.