06983f1996-09-22Fredrik Hübinette (Hubbe) This is what you need to do to install Pike:
5267b71995-08-09Fredrik Hübinette (Hubbe)  1) Run ./configure, this is a sh script that will generate machine.h and
51bd9e1996-10-09Fredrik Hübinette (Hubbe)  Makefile from machine.h.in and Makefile.in. Some options for ./configure are:
8cfc391997-11-29Fredrik Hübinette (Hubbe)  --prefix=/foo/bar if you want to install Pike in /foo/bar, default is /usr/local. --without-gdbm compile without gdbm support --without-gmp compile without gmp support --without-debug compile without runtime debugging --without-threads compile without threads support --without-zlib compile without gzip compression libary support --without-dynamic-modules compile statically, no dynamic loading used. (makes binary larger) --without-mysql compile without mysql support --with-profiling enables profiling pike code but slows down interpreter a little
51bd9e1996-10-09Fredrik Hübinette (Hubbe)  You might also want to set the following environment variables: CFLAGS Put extra flags for your C compiler here. CPPFLAGS Put extra flags for your C preprocessor here (such as -I/usr/gnu/include) LDFLAGS Put extra flags to your linker here, such as -L/usr/gnu/lib and -R/usr/gnu/lib
1998451996-11-19David Hedbor  Use the above flags to make sure the configure script finds the
ac10221999-03-13Marcus Comstedt  gdbm and gmp libraries and include files if you need or want those modules. If the configure script doesn't find them, Pike will still compile, but without those modules.
51bd9e1996-10-09Fredrik Hübinette (Hubbe)  2) If needed, edit config.h and Makefile to suit your purposes.
5267b71995-08-09Fredrik Hübinette (Hubbe)  I've tried to make it so that you don't have to change config.h or
51bd9e1996-10-09Fredrik Hübinette (Hubbe)  Makefile at all. If you need to do what you consider 'unnessecary
1998451996-11-19David Hedbor  changes' then mail me and I'll try to fit it into configure. If possible, use gnu make, gcc, gnu sed and bison.
5267b71995-08-09Fredrik Hübinette (Hubbe)  3) Run make. 4) optionally, run 'make verify' to check that the compiled driver works
1998451996-11-19David Hedbor  as it should (might be a good idea) This will take a little time and use quite a lot of memory, because the testprogram is quite large. If everything works out fine no extra messages are written.
5267b71995-08-09Fredrik Hübinette (Hubbe) 
06983f1996-09-22Fredrik Hübinette (Hubbe) 5) If you want to install Pike, write 'make install'
5267b71995-08-09Fredrik Hübinette (Hubbe) 
8ce9ad1996-05-16Fredrik Hübinette (Hubbe) 6) Optionally do 'make html_docs' to create a directory called docs which
06983f1996-09-22Fredrik Hübinette (Hubbe)  will contain the Pike documentation in html. This directory can then
8ce9ad1996-05-16Fredrik Hübinette (Hubbe)  be copied to anywhere you want.
5267b71995-08-09Fredrik Hübinette (Hubbe)  What to do when it doesn't work: 1) Try again.
2a50101995-11-06Fredrik Hübinette (Hubbe) 2) Your sh might be too buggy to run ./configure. (This is the case on A/UX) Try using bash, zsh or possibly ksh. To use bash, first run /bin/sh and type: $ CONFIG_SHELL=full_path_for_bash $ export CONFIG_SHELL $ $CONFIG_SHELL ./configure 3) ./configure relies heavily on sed, if you have several sed in your path
5267b71995-08-09Fredrik Hübinette (Hubbe)  try another sed. (preferably gnu sed)
2a50101995-11-06Fredrik Hübinette (Hubbe) 4) configure might have done something wrong, check machine.h and report
5267b71995-08-09Fredrik Hübinette (Hubbe)  any errors back to me.
ac10221999-03-13Marcus Comstedt 5) Your gmp/gdbm libraries might not be working or incorrectly
51bd9e1996-10-09Fredrik Hübinette (Hubbe)  installed, start over by running configure with the approperiate
eec1371996-11-02Fredrik Hübinette (Hubbe)  --without-xxx arguments. Also note that threads might give problems with I/O and signals. If so you need to run configure --without-threads.
51bd9e1996-10-09Fredrik Hübinette (Hubbe)  6) Try a different compiler, malloc, compiler-compiler and/or make.
5267b71995-08-09Fredrik Hübinette (Hubbe)  (if you have any other)
8cfc391997-11-29Fredrik Hübinette (Hubbe) 7) On old Linux Slackware machines (older than slackware 3.0), Pike sometimes
2a50101995-11-06Fredrik Hübinette (Hubbe)  fails to find -lm, this is because of a bug in /usr/lib/libm.sa (or possibly libg.a) in slackware.
bf4a8d1995-10-20Fredrik Hübinette (Hubbe)  Compile with 'make EXTRALIBS="-lc -lm"' to get around this bug.
ccc2d41997-04-10Fredrik Hübinette (Hubbe)  Threads support on linux works on some releaes, you might need to add an _ to line 36 in /usr/include/sched.h (change _P to __P).
51bd9e1996-10-09Fredrik Hübinette (Hubbe) 8)
5267b71995-08-09Fredrik Hübinette (Hubbe) If you find a bug in the interpreter, the first thing to do is to make sure
71f3a21998-11-22Fredrik Hübinette (Hubbe) the interpreter is compiled with PIKE_DEBUG defined. If not recompile with PIKE_DEBUG
5267b71995-08-09Fredrik Hübinette (Hubbe) and see if you get another error. When you've done this, please report the
8cfc391997-11-29Fredrik Hübinette (Hubbe) bug to hubbe@hubbe.net and include as much as you can muster of the
2a50101995-11-06Fredrik Hübinette (Hubbe) following:
5267b71995-08-09Fredrik Hübinette (Hubbe) 
8cfc391997-11-29Fredrik Hübinette (Hubbe)  o The version of the driver. (Try pike --version or look in src/version.c)
5267b71995-08-09Fredrik Hübinette (Hubbe)  o What kind of system hardware/software you use (OS, compiler, etc.) o the piece of code that crashes or bugs.
06983f1996-09-22Fredrik Hübinette (Hubbe)  (preferably in a very small pike-script with the bug isolated)
5267b71995-08-09Fredrik Hübinette (Hubbe)  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 me a backtrace and dump of vital variables at the point of crash. o or, if you found the error and corrected it, just send me the bugfix along with a description of what you did and why.
cb22561995-10-11Fredrik Hübinette (Hubbe)  /Fredrik Hubinette