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
  
Pike by Fredrik Hübinette 1994-2001 and the Pike team 2001-2017 
 
Permission to copy, modify, and distribute this source for any legal 
purpose granted as long as my name is still attached to it.  More 
specifically, the GPL, LGPL and MPL licenses apply to this software. 
 
New releases can be found on http://pike.lysator.liu.se/download/ 
Report bugs at http://bugs.roxen.com/ 
There is also a mailing list, to subscribe to it mail: 
pike-request@roxen.com 
 
 
HOW TO BUILD PIKE 
 
If you are building Pike from git, read README-GIT instead. 
 
The top-level makefile (in this directory, not the src directory) has 
all the magic you need to build Pike. Just type 'make'. 
To install type "make install" or "make install_interactive". 
 
You will need a C compiler and libgmp. You probably also want to have 
GNU make and libnettle. 
 
If that doesn't work, refer to README-GIT, in particular the sections 
on additional "DEPENDENCIES", on "CONFIGURE OPTIONS AND BUILD VARIABLES", 
on "MANUAL BUILDING" and, if needed, the section "IF IT DOESN'T WORK". 
 
 
BUGS 
 
If you find a bug in the interpreter, the first thing to do is to make 
sure the interpreter is compiled with PIKE_DEBUG defined.  If not, 
recompile with PIKE_DEBUG and see if you get another error.  When 
you've done this, please report the bug to us at 
http://bugs.roxen.com/ and include as much as you can muster of the 
following: 
 
  o The version of the driver. (Try pike --version or look in 
    src/version.h) 
  o What kind of system hardware/software you use (OS, compiler, etc.) 
  o The piece of code that crashes or bugs, preferably in a very 
    small Pike-script with the bug isolated.  Please send a complete 
    running example of something that makes the interpreter bug. 
  o A description of what it is that bugs and when. 
  o If you know how, then also give us a backtrace and dump of vital 
    variables at the point of crash. 
  o Or, if you found the error and corrected it, just send us the 
    bugfix along with a description of what you did and why.