pike.git / src / README

version» Context lines:

pike.git/src/README:13:    --without-threads compile without threads support    --without-zlib compile without gzip compression libary support       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 sill compile, -  but without those modules. +  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.      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. +  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 -  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. +  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.      5) If you want to install Pike, write 'make install'      6) Optionally do 'make html_docs' to create a directory called docs which    will contain the Pike documentation in html. This directory can then    be copied to anywhere you want.      What to do when it doesn't work:   1) Try again.