Author

Topic: Compiling on OSX (Read 715 times)

hero member
Activity: 896
Merit: 1006
November 09, 2016, 05:51:03 AM
#5
I know it's not exactly what you asked for, but i did use the gitian method to compile bitcoin core for mac OSX (just for fun, since i don't own any apple products, i never tested out my build).

If i remember it correctly, if you followed the procedure for building with gitian to the letter (every detail, including the version of debian and package versions), you ended up with all binaries compiles for windows 32 bit, windows 64 bit, linux 32 bit, linux 64 bit and mac.
newbie
Activity: 3
Merit: 0
November 09, 2016, 05:47:43 AM
#4
Thank you for putting this together! This worked for me, and saved me from several days of headache with clang.
Zz
legendary
Activity: 1820
Merit: 1077
November 07, 2016, 05:44:35 AM
#3
do not compile
Set up as ready.
1. Go to https://bitcoin.org/en/download
Once you're there, click on "Mac OS X".
2. clik to download https://bitcoin.org/bin/bitcoin-core-0.13.1/bitcoin-0.13.1-osx64.tar.gz

3. run terminal

4. tar zxvf bitcoin-0.13.1-osx64.tar.gz
5. double clik to dmg file
6. Drag Bitcoin-Qt to Applications
Go to Applications folder, double click on Bitcoin-Qt, you'll see it starts verifying blocks and the wallet will be ready within an hour as it continue to synchronize with network.
staff
Activity: 3458
Merit: 6793
Just writing some code
November 06, 2016, 11:07:16 PM
#2
What commands did you run?
newbie
Activity: 1
Merit: 0
November 06, 2016, 11:00:56 PM
#1
hi there, I am attempting to compile bitcoin code on OSX Sierra 10.12.1, and get this error:

AR       leveldb/libmemenv.a
  CXXLD    bitcoind
Undefined symbols for architecture x86_64:
  "Db::verify(char const*, char const*, std::basic_ostream >*, unsigned int)", referenced from:
      CDBEnv::Verify(std::basic_string, std::allocator > const&, bool (*)(CDBEnv&, std::basic_string, std::allocator > const&)) in libbitcoin_wallet.a(libbitcoin_wallet_a-db.o)

Any pointers into resolving this? Apologies if this is not the correct forum.
Jump to: