ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-21 12:15:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

rippled 1.3.0 requires Boost 1.70 (as of rc2)

Browse Source
This commit is contained in:
mDuo13
2019-07-11 01:29:58 -07:00
parent 874cbb5b46
commit 92bf45afa2
2 changed files with 18 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md
View File

@@ -24,9 +24,9 @@ For development purposes Ripple recommends running `rippled` as your own user, n
$ brew install git cmake pkg-config protobuf openssl ninja $ brew install git cmake pkg-config protobuf openssl ninja
0. Install Boost 1.67.0 or higher. `rippled` 1.3.0 is compatible with Boost 1.67.0 and higher. The latest version of Boost available in the Homebrew repositories isn't new enough, so you must install Boost manually: 0. Install Boost 1.70.0 or higher. `rippled` 1.3.0 is compatible with Boost 1.70.0 and higher. The latest version of Boost available in the Homebrew repositories isn't new enough, so you must install Boost manually:
1. Download [Boost 1.67.0](https://dl.bintray.com/boostorg/release/1.67.0/source/boost_1_67_0.tar.bz2). 1. Download [Boost 1.70.0](https://dl.bintray.com/boostorg/release/1.70.0/source/boost_1_70_0.tar.bz2).
2. Extract it to a folder. Be sure to note the location. 2. Extract it to a folder. Be sure to note the location.
@@ -38,7 +38,7 @@ For development purposes Ripple recommends running `rippled` as your own user, n
0. Ensure that your `BOOST_ROOT` environment variable points to the directory created by the Boost installation. To find your Boost install directory, use `brew info boost`. Put this environment variable in your `.bash_profile` file so it's automatically set when you log in. For example: 0. Ensure that your `BOOST_ROOT` environment variable points to the directory created by the Boost installation. To find your Boost install directory, use `brew info boost`. Put this environment variable in your `.bash_profile` file so it's automatically set when you log in. For example:
export BOOST_ROOT=/Users/my_user/boost_1_67_0 export BOOST_ROOT=/Users/my_user/boost_1_70_0
0. If you updated your `.bash_profile` file in the previous step, be sure to source it. For example: 0. If you updated your `.bash_profile` file in the previous step, be sure to source it. For example:

31
content/tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md
View File

@@ -44,21 +44,21 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof
5. Compile Boost. 5. Compile Boost.
Version 1.3.0 of `rippled` requires Boost version 1.67.0 or higher. Because Boost version 1.67.0 or higher isn't available in the Ubuntu 18.04 (or 16.04) software repositories, you must compile it yourself. Version 1.3.0 of `rippled` requires Boost version 1.70.0 or higher. Because Boost version 1.70.0 or higher isn't available in the Ubuntu 18.04 (or 16.04) software repositories, you must compile it yourself.
If you have previously built Boost 1.67.0 for `rippled` and configured the `BOOST_ROOT` environment variable, you can skip these steps. If you have previously built Boost 1.70.0 for `rippled` and configured the `BOOST_ROOT` environment variable, you can skip these steps.
1. Download Boost 1.67.0. 1. Download Boost 1.70.0.
wget https://dl.bintray.com/boostorg/release/1.67.0/source/boost_1_67_0.tar.gz wget https://dl.bintray.com/boostorg/release/1.70.0/source/boost_1_70_0.tar.gz
2. Extract `boost_1_67_0.tar.gz`. 2. Extract `boost_1_70_0.tar.gz`.
tar xvzf boost_1_67_0.tar.gz tar xvzf boost_1_70_0.tar.gz
3. Change to the new `boost_1_67_0` directory. 3. Change to the new `boost_1_70_0` directory.
cd boost_1_67_0 cd boost_1_70_0
4. Prepare the Boost.Build system for use. 4. Prepare the Boost.Build system for use.
@@ -70,9 +70,9 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof
**Tip:** This example uses 4 processes to build in parallel. The best number of processes to use depends on how many CPU cores your hardware has available. You can use `cat /proc/cpuinfo` to get information about your hardware's processor. **Tip:** This example uses 4 processes to build in parallel. The best number of processes to use depends on how many CPU cores your hardware has available. You can use `cat /proc/cpuinfo` to get information about your hardware's processor.
6. Set the environment variable `BOOST_ROOT` to point to the new `boost_1_67_0` directory. It's best to put this environment variable in your `.profile`, or equivalent, file for your shell so it's automatically set when you log in. Add the following line to the file: 6. Set the environment variable `BOOST_ROOT` to point to the new `boost_1_70_0` directory. It's best to put this environment variable in your `.profile`, or equivalent, file for your shell so it's automatically set when you log in. Add the following line to the file:
export BOOST_ROOT=/home/my_user/boost_1_67_0 export BOOST_ROOT=/home/my_user/boost_1_70_0
7. Source your updated `.profile` file. For example: 7. Source your updated `.profile` file. For example:
@@ -86,15 +86,14 @@ These instructions use Ubuntu's APT (Advanced Packaging Tool) to install the sof
7. Check the commit log to be sure you're compiling the version you intend to. The most recent commit should be signed by a well-known Ripple developer and should set the version number to the latest released version. For example: 7. Check the commit log to be sure you're compiling the version you intend to. The most recent commit should be signed by a well-known Ripple developer and should set the version number to the latest released version. For example:
***TODO: Add the 1.3.0 release commit***
$ git log -1 $ git log -1
commit 7779dcdda00ea61a976cf5f387bc1f3bb4ebbfdd commit caa5c9e2232ff1eee1d0c61907283649e48e6fbc
Author: Mike Ellery <mellery451@gmail.com> Author: Nik Bougalis <nikb@bougalis.net>
Date: Tue Feb 12 16:41:03 2019 -0800 Date: Tue Jul 9 13:56:37 2019 -0700
Set version to 1.3.0
Set version to 1.2.0
8. If you previously built, or (more importantly) tried and failed to build `rippled`, you should delete the `my_build/` directory (or whatever you named it) to start clean before moving on to the next step. Otherwise, you may get unexpected behavior, like a `rippled` executable that crashes due to a segmentation fault (segfault). 8. If you previously built, or (more importantly) tried and failed to build `rippled`, you should delete the `my_build/` directory (or whatever you named it) to start clean before moving on to the next step. Otherwise, you may get unexpected behavior, like a `rippled` executable that crashes due to a segmentation fault (segfault).