Skip to content

Commit

Permalink
RocksDB now requires gflags v2.2.0 (facebook#10933)
Browse files Browse the repository at this point in the history
Summary: Pull Request resolved: facebook#10933

Reviewed By: jaykorean

Differential Revision: D49872302

Pulled By: jowlyzhang

fbshipit-source-id: 15f4e177bed59455ff58a0b48a3f6a55973d0b38
  • Loading branch information
adamretter authored and facebook-github-bot committed Oct 3, 2023
1 parent 97f6f47 commit c13569e
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions INSTALL.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ There are few options when compiling RocksDB:
* `make check` will compile and run all the unit tests. `make check` will compile RocksDB in debug mode.

* `make all` will compile our static library, and all our tools and unit tests. Our tools
depend on gflags. You will need to have gflags installed to run `make all`. This will compile RocksDB in debug mode. Don't
depend on gflags 2.2.0 or newer. You will need to have gflags installed to run `make all`. This will compile RocksDB in debug mode. Don't
use binaries compiled by `make all` in production.

* By default the binary we produce is optimized for the CPU you're compiling on
Expand Down Expand Up @@ -77,7 +77,7 @@ most processors made since roughly 2013.

git clone https://github.com/gflags/gflags.git
cd gflags
git checkout v2.0
git checkout v2.2.0
./configure && make && sudo make install

**Notice**: Once installed, please add the include path for gflags to your `CPATH` environment variable and the
Expand Down

0 comments on commit c13569e

Please sign in to comment.