Skip to content
Snippets Groups Projects
Commit 8991a472 authored by Martin Nilsson's avatar Martin Nilsson
Browse files

Removed CVS statement that has confused at least one potential Pike user.... 

Removed CVS statement that has confused at least one potential Pike user. Don't mention make depend in the normal build procedure.

Rev: README:1.17
parent ae9bd2ed
No related branches found
No related tags found
No related merge requests found
Show whitespace changes
Inline Side-by-side
Showing
with 8 additions and 10 deletions
README
+ 8
− 10
View file @ 8991a472
...@@ -13,8 +13,7 @@ pike-request@roxen.com ...@@ -13,8 +13,7 @@ pike-request@roxen.com
HOW TO BUILD PIKE HOW TO BUILD PIKE
The top-level makefile (in this directory, not the src directory) has The top-level makefile (in this directory, not the src directory) has
all the magic you need to build pike directly from CVS. Just type all the magic you need to build Pike. Just type 'make'.
'make'.
You will need autoconf, gnu m4, bison, a C compiler and the GMP You will need autoconf, gnu m4, bison, a C compiler and the GMP
library. You probably also want to use GNU make and libz. library. You probably also want to use GNU make and libz.
...@@ -70,24 +69,21 @@ yourself, try the Old instructions: ...@@ -70,24 +69,21 @@ yourself, try the Old instructions:
modules. If the configure script doesn't find them, Pike will modules. If the configure script doesn't find them, Pike will
still compile, but without those modules. still compile, but without those modules.
4) Run 'make depend' 4) If needed, edit config.h and Makefile to suit your purposes. I've
This updates all the Makefile.in files in the source dir to contain
the correct dependencies
5) 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 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 'unnecessary Makefile at all. If you need to do what you consider 'unnecessary
changes' then mail us and we'll try to fit it into configure. If changes' then mail us and we'll try to fit it into configure. If
possible, use gnu make, gcc, gnu sed and bison possible, use gnu make, gcc, gnu sed and bison
6) Run 'make' 5) Run 'make'
This builds pike. This builds pike.
7) Optionally, run 'make verify' to check that the compiled driver 6) Optionally, run 'make verify' to check that the compiled driver
works as it should (might be a good idea). This will take a little works as it should (might be a good idea). This will take a little
time and use quite a lot of memory, because the test program is time and use quite a lot of memory, because the test program is
quite large. If everything works out fine no extra messages are quite large. If everything works out fine no extra messages are
written. written. You will need GNU m4 for this stage to generate the test
case files.
8) If you want to install Pike, write 'make install'. This will put 8) If you want to install Pike, write 'make install'. This will put
your pike in <prefix>/pike/<version>/. This way, you can install your pike in <prefix>/pike/<version>/. This way, you can install
...@@ -105,6 +101,8 @@ IF IT DOESN'T WORK: ...@@ -105,6 +101,8 @@ IF IT DOESN'T WORK:
o Try again. o Try again.
o Try running 'make depend'.
o Your sh might be too buggy to run ./configure. (This is the case on o 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 A/UX) Try using bash, zsh or possibly ksh. To use bash, first run
/bin/sh and /bin/sh and
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment