Skip to content

Commit a3a80c2

Browse files
committed
remove berkeley-db4 workaround
"brew install berkeley-db4" appears to be working again. simplified instructions by removing the berkeley-db4 workaround.
1 parent c1fb0e1 commit a3a80c2

File tree

1 file changed

+1
-24
lines changed

1 file changed

+1
-24
lines changed

doc/build-osx.md

Lines changed: 1 addition & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -32,33 +32,10 @@ Instructions: Homebrew
3232

3333
#### Install dependencies using Homebrew
3434

35-
brew install autoconf automake libtool boost miniupnpc openssl pkg-config protobuf qt5
35+
brew install autoconf automake berkeley-db4 libtool boost miniupnpc openssl pkg-config protobuf qt5
3636

3737
NOTE: Building with Qt4 is still supported, however, could result in a broken UI. As such, building with Qt5 is recommended.
3838

39-
#### Installing berkeley-db4 using Homebrew
40-
41-
The homebrew package for berkeley-db4 has been broken for some time. It will install without Java though.
42-
43-
Running this command takes you into brew's interactive mode, which allows you to configure, make, and install by hand:
44-
```
45-
$ brew install https://raw.github.com/homebrew/homebrew/master/Library/Formula/berkeley-db4.rb -–without-java
46-
```
47-
48-
The rest of these commands are run inside brew interactive mode:
49-
```
50-
/private/tmp/berkeley-db4-UGpd0O/db-4.8.30 $ cd ..
51-
/private/tmp/berkeley-db4-UGpd0O $ db-4.8.30/dist/configure --prefix=/usr/local/Cellar/berkeley-db4/4.8.30 --mandir=/usr/local/Cellar/berkeley-db4/4.8.30/share/man --enable-cxx
52-
/private/tmp/berkeley-db4-UGpd0O $ make
53-
/private/tmp/berkeley-db4-UGpd0O $ make install
54-
/private/tmp/berkeley-db4-UGpd0O $ exit
55-
```
56-
57-
After exiting, you'll get a warning that the install is keg-only, which means it wasn't symlinked to `/usr/local`. You don't need it to link it to build bitcoin, but if you want to, here's how:
58-
59-
$ brew link --force berkeley-db4
60-
61-
6239
### Building `bitcoind`
6340

6441
1. Clone the github tree to get the source code and go into the directory.

0 commit comments

Comments
 (0)