Raymond Toy pushed to branch master at cmucl / cmucl

Commits:

1 changed file:

Changes:

  • BUILDING.md
    ... ... @@ -48,17 +48,20 @@ Setting up a build environment
    48 48
     ------------------------------
    
    49 49
     
    
    50 50
     1. Create a base directory and change to it
    
    51
    -
    
    51
    +```
    
    52 52
         mkdir cmucl ; cd cmucl
    
    53
    -
    
    53
    +```
    
    54 54
     2. Fetch the sources and put them into the base directory
    
    55 55
     ```
    
    56 56
         tar xzf /tmp/cmucl-source.tar.gz
    
    57 57
     ```
    
    58
    +
    
    58 59
         or, if you want to use the git sources directly:
    
    60
    +
    
    59 61
     ```
    
    60 62
         git clone https://gitlab.common-lisp.net/cmucl/cmucl.git
    
    61 63
     ```
    
    64
    +
    
    62 65
         Whatever you do, the sources must be in a directory named src
    
    63 66
         inside the base directory.  Since the build tools keep all
    
    64 67
         generated files in separate target directories, the src directory
    
    ... ... @@ -81,7 +84,9 @@ quick guide.
    81 84
        Use this to build from a version of CMUCL that is very close to the
    
    82 85
        sources you are trying to build now:
    
    83 86
     
    
    87
    +```
    
    84 88
        bin/build.sh -C "" -o "<name-of-old-lisp> <options-to-lisp>"
    
    89
    +```
    
    85 90
     
    
    86 91
        This will build CMUCL 3 times, each time with the result of the
    
    87 92
        previous build.  The last time, the additional libraries like CLX,
    
    ... ... @@ -100,7 +105,9 @@ quick guide.
    100 105
     
    
    101 106
        For these, you can use this:
    
    102 107
     
    
    108
    +```
    
    103 109
        bin/build.sh -C "" -o "<old-lisp>" -B boot1.lisp -B boot2.lisp
    
    110
    +```
    
    104 111
     
    
    105 112
        The bootstrap files listed with the -B option (as many as needed)
    
    106 113
        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 128
     building from, then you need to use b) or c) above.  You may need to
    
    122 129
     read the bootfiles for additional instructions, if any.  
    
    123 130
     
    
    124
    -If there are no bootfiles, then you can use a) above.
    
    131
    +If there are no bootfiles, then you can use 1. above.
    
    125 132
     
    
    126
    -The build.sh script supports other options, and bin/build.sh -?
    
    133
    +The `build.sh` script supports other options, and `bin/build.sh -?`
    
    127 134
     will give a quick summary.  Read bin/build.sh for more
    
    128 135
     information. 
    
    129 136
     
    
    ... ... @@ -373,10 +380,12 @@ Overview of the included build scripts
    373 380
     
    
    374 381
         The remaining arguments used to create the name of the tarfiles.  The
    
    375 382
         names will have the form:
    
    383
    +
    
    376 384
     ```
    
    377 385
        cmucl-<version>-<arch>-<os>.tar.bz2
    
    378 386
        cmucl-<version>-<arch>-<os>.extras.tar.bz2
    
    379 387
     ```
    
    388
    +
    
    380 389
         Of course, the "bz2" will be "gz" if you specified gzip compression
    
    381 390
         instead of bzip.
    
    382 391
     
    
    ... ... @@ -695,4 +704,4 @@ In particular steps 3, 4, and 5 can be combined into one by using the
    695 704
     -c, -r, and -l options for cross-build-world.sh.  The -c option cleans
    
    696 705
     out the targe and cross directories; -r does step 4; and -l does step
    
    697 706
     5.
    
    698
    -===============
    707
    +