pike.git / src / README

version» Context lines:

pike.git/src/README:1:   This is what you need to do to install Pike:      1) Run ./configure, this is a sh script that will generate machine.h and    Makefile from machine.h.in and Makefile.in.       Some options for ./configure are:    --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-readline compile without readline 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       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       Use the above flags to make sure the configure script finds the -  gdbm, gmp and readline 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. +  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.      2) If needed, edit config.h and Makefile to suit your purposes.    I've tried to make it so that you don't have to change config.h or    Makefile at all. If you need to do what you consider 'unnessecary    changes' then mail me and I'll try to fit it into configure. If    possible, use gnu make, gcc, gnu sed and bison.      3) Run make.      4) optionally, run 'make verify' to check that the compiled driver works
pike.git/src/README:58:    $ 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    try another sed. (preferably gnu sed)      4) configure might have done something wrong, check machine.h and report    any errors back to me.    - 5) Your gmp/readline/gdbm libraries might not be working or incorrectly + 5) Your gmp/gdbm libraries might not be working or incorrectly    installed, start over by running configure with the approperiate    --without-xxx arguments. Also note that threads might give problems    with I/O and signals. If so you need to run configure --without-threads.      6) Try a different compiler, malloc, compiler-compiler and/or make.    (if you have any other)      7) On old Linux Slackware machines (older than slackware 3.0), Pike sometimes    fails to find -lm, this is because of a bug in /usr/lib/libm.sa    (or possibly libg.a) in slackware.