Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
cmucl
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
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
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
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Carl Shapiro
cmucl
Commits
d9487768
Commit
d9487768
authored
6 years ago
by
Raymond Toy
Browse files
Options
Downloads
Patches
Plain Diff
More markup fixes
parent
15655145
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
BUILDING.md
+14
-5
14 additions, 5 deletions
BUILDING.md
with
14 additions
and
5 deletions
BUILDING.md
+
14
−
5
View file @
d9487768
...
@@ -48,17 +48,20 @@ Setting up a build environment
...
@@ -48,17 +48,20 @@ Setting up a build environment
------------------------------
------------------------------
1.
Create a base directory and change to it
1.
Create a base directory and change to it
```
mkdir cmucl ; cd cmucl
mkdir cmucl ; cd cmucl
```
2.
Fetch the sources and put them into the base directory
2.
Fetch the sources and put them into the base directory
```
```
tar xzf /tmp/cmucl-source.tar.gz
tar xzf /tmp/cmucl-source.tar.gz
```
```
or, if you want to use the git sources directly:
or, if you want to use the git sources directly:
```
```
git clone https://gitlab.common-lisp.net/cmucl/cmucl.git
git clone https://gitlab.common-lisp.net/cmucl/cmucl.git
```
```
Whatever you do, the sources must be in a directory named src
Whatever you do, the sources must be in a directory named src
inside the base directory. Since the build tools keep all
inside the base directory. Since the build tools keep all
generated files in separate target directories, the src directory
generated files in separate target directories, the src directory
...
@@ -81,7 +84,9 @@ quick guide.
...
@@ -81,7 +84,9 @@ quick guide.
Use this to build from a version of CMUCL that is very close to the
Use this to build from a version of CMUCL that is very close to the
sources you are trying to build now:
sources you are trying to build now:
```
bin/build.sh -C "" -o "<name-of-old-lisp> <options-to-lisp>"
bin/build.sh -C "" -o "<name-of-old-lisp> <options-to-lisp>"
```
This will build CMUCL 3 times, each time with the result of the
This will build CMUCL 3 times, each time with the result of the
previous build. The last time, the additional libraries like CLX,
previous build. The last time, the additional libraries like CLX,
...
@@ -100,7 +105,9 @@ quick guide.
...
@@ -100,7 +105,9 @@ quick guide.
For these, you can use this:
For these, you can use this:
```
bin/build.sh -C "" -o "<old-lisp>" -B boot1.lisp -B boot2.lisp
bin/build.sh -C "" -o "<old-lisp>" -B boot1.lisp -B boot2.lisp
```
The bootstrap files listed with the -B option (as many as needed)
The bootstrap files listed with the -B option (as many as needed)
are loaded in order, so be sure to get them right.
are loaded in order, so be sure to get them right.
...
@@ -121,9 +128,9 @@ file date of a boot file is later than the version of CMUCL you are
...
@@ -121,9 +128,9 @@ file date of a boot file is later than the version of CMUCL you are
building from, then you need to use b) or c) above. You may need to
building from, then you need to use b) or c) above. You may need to
read the bootfiles for additional instructions, if any.
read the bootfiles for additional instructions, if any.
If there are no bootfiles, then you can use
a)
above.
If there are no bootfiles, then you can use
1.
above.
The build.sh script supports other options, and bin/build.sh -?
The
`
build.sh
`
script supports other options, and
`
bin/build.sh -?
`
will give a quick summary. Read bin/build.sh for more
will give a quick summary. Read bin/build.sh for more
information.
information.
...
@@ -373,10 +380,12 @@ Overview of the included build scripts
...
@@ -373,10 +380,12 @@ Overview of the included build scripts
The remaining arguments used to create the name of the tarfiles. The
The remaining arguments used to create the name of the tarfiles. The
names will have the form:
names will have the form:
```
```
cmucl-<version>-<arch>-<os>.tar.bz2
cmucl-<version>-<arch>-<os>.tar.bz2
cmucl-<version>-<arch>-<os>.extras.tar.bz2
cmucl-<version>-<arch>-<os>.extras.tar.bz2
```
```
Of course, the "bz2" will be "gz" if you specified gzip compression
Of course, the "bz2" will be "gz" if you specified gzip compression
instead of bzip.
instead of bzip.
...
@@ -695,4 +704,4 @@ In particular steps 3, 4, and 5 can be combined into one by using the
...
@@ -695,4 +704,4 @@ In particular steps 3, 4, and 5 can be combined into one by using the
-c, -r, and -l options for cross-build-world.sh. The -c option cleans
-c, -r, and -l options for cross-build-world.sh. The -c option cleans
out the targe and cross directories; -r does step 4; and -l does step
out the targe and cross directories; -r does step 4; and -l does step
5.
5.
===============
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