blob: df74e00c8d6c3ed1def7cfecac7454dd7beed6e2 [file] [log] [blame]
Guido van Rossum627b2d71993-12-24 10:39:16 +00001This is an ALPHA release of Python 1.0 for UNIX. Currently it builds
2a rather minimal executable and requires that you already have Python
30.9.9 (or at least its library).
4
5Instructions for building:
6
7(1) Run the configure shell script:
8
9 ./configure
10
11This may take a minute or two -- it does a rather thorough
12investigation of your system to find out many compile-time flags. It
13prints messages but does not ask questions. When finished, it will
14create config.status in the current directory, as well as Makefile in
15each of the subdirectories Parser, Objects and Python. Note that
16unless you have the CC shell environment variable set to the name of
17your C compiler, it will attempt to find the GNU C compiler (gcc) and
18use it if it finds it. On some systems a broken gcc may be installed;
19put CC=cc in the environment to override it. On some systems it may
20be interesting to compare both compilers. (Note: the Makefile has
21been rigged in such a way that it will run configure if you haven't
22done so.)
23
24(2) Run Make:
25
26 make
27
28This will recursively run Make in each of the Parser, Objects and
29Python subdirectories. In Parser it builds an executable "pgen" and a
30library libParser.a. In Objects it builds a library libObjects.a. In
31Python it builds a library libPython.a and an executable "python".
32
33(3) Test the resulting executable:
34
35 Python/python -c 'import testall'
36
37For now, this will assume that you have a working version of Python
38release 0.9.9 installed in /usr/local (it uses the Python library from
39/usr/local/lib/python) or that your PYTHONPATH shell environment
40variable points to the 0.9.9 Python library.
41
42(4) Optionally: read Extensions/README and try to build a Python with
43all the extensions that make sense on your system. (Note: some
44extensions are not supported yet.)
45
46(5) Give feedback:
47
48 Mail guido@cwi.nl
49
50Please tell me whether the build succeeded or not. If you needed to
51edit *any* file, tell me which file, why and how (send me a diff or a
52copy of the modified file if you can). If you get stuck, please send
53me the error output. Don't forget to mention the operating system,
54compiler and hardware version that you used, e.g. "Solaris 2.2 with
55gcc version cygnus-2.0.2 on a dual processor Sparcstation 10" or "IRIX
565.1 with standard cc on an Indigo XS-24 with R4000 CPU". If you can
57build the core interpreter but get stuck building an extended version,
58let me know which extensions gave problems and how.
59
60--Guido van Rossum, CWI, Amsterdam <Guido.van.Rossum@cwi.nl>
61URL: <http://www.cwi.nl/cwi/people/Guido.van.Rossum.html>