Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
pike
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pikelang
pike
Commits
67f820ae
Commit
67f820ae
authored
23 years ago
by
Johan Sundström
Browse files
Options
Downloads
Patches
Plain Diff
Fixed wording.
Rev: README-CVS.txt:1.17
parent
8e4f3631
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README-CVS.txt
+4
-4
4 additions, 4 deletions
README-CVS.txt
with
4 additions
and
4 deletions
README-CVS.txt
+
4
−
4
View file @
67f820ae
$Id: README-CVS.txt,v 1.1
6
2002/04/11 0
1:24:48 mast
Exp $
$Id: README-CVS.txt,v 1.1
7
2002/04/11 0
6:12:08 jhs
Exp $
HOW TO BUILD PIKE FROM CVS
If you like to live at the bleeding edge you can download pike from CVS
w
h
ith all the latest additions from the developers. There are two
with all the latest additions from the developers. There are two
major branches in the archive, the latest stable branch and latest
development branch. Stable versions have an even minor version number,
i.e. 7.0.x, 7.2.x, 7.4.x, whereas the development branches have an odd
...
...
@@ -138,8 +138,8 @@ Instructions if you want to do the build more manually:
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'v
e
tried to make it so that you don't have to change config.h or
5. If needed, edit config.h and Makefile to suit your purposes.
W
e
have
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
changes' then mail us and we'll try to fit it into configure. If
possible, use gnu make, gcc, gnu sed and bison.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment