aboutsummaryrefslogtreecommitdiff
path: root/README.rst
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2011-06-14 08:13:29 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2011-06-14 08:18:31 +0200
commit5363cb05f682a7954b6fa5c74fbe589c41b955e3 (patch)
tree14beb16b4c38a4e087615eb208b56bd7f872eb93 /README.rst
parentf15df6bb7a470f75ca61f8c9ddcebfbb39a76f49 (diff)
Add berkelydb version warning
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst15
1 files changed, 15 insertions, 0 deletions
diff --git a/README.rst b/README.rst
index 2ffc4a92b8..9d7ad10f18 100644
--- a/README.rst
+++ b/README.rst
@@ -60,3 +60,18 @@ Alternatively, install Qt Creator and open the `bitcoin-qt.pro` file.
An executable named `bitcoin-qt` will be built.
+Berkely DB version warning
+==========================
+
+A warning for people using the *static binary* version of Bitcoin (tl;dr: **Berkely DB databases are not forward compatible**).
+
+The static binary version of Bitcoin is linked against libdb4.7 or libdb4.8 (see also `this Debian issue`_).
+
+Now the nasty thing is that databases from 5.X are not compatible with 4.X.
+
+If the globally installed development package of Berkely DB installed on your system is 5.X, any source you
+build yourself will be linked against that. The first time you run with a 5.X version the database will be upgraded,
+and 4.X cannot open the new format. This means that you cannot go back to the old statically linked version without
+significant hassle!
+
+.. _`this Debian issue`: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621425