Instructions for building with OSX needs more clarity

[bacongobbler]

I'm trying to go through the instructions on building dogecoind on OSX 10.9.1, but I'm completely lost on this step:

• link the statics to /usr/local/lib/

I'm not too saavy with boost, but I'm interested in developing a Ruby wrapper around dogecoind so that I can make RPCs from a web application. Has anyone been able to build dogecoind on Mavericks, and if so, how do I "link the statics" that were built after compiling boost?

Once I get this all working nicely on my laptop, I'd be happy to submit a PR to improve the documentation :)

[bacongobbler]

I found out that dogecoin-qt can be used to make RPCs as long as you make a couple changes to ~/Library/Application\ Support/Dogecoin/dogecoin.conf, so I'm using that as a workaround.

[bacongobbler]

I found out that dogecoin-qt can be used to make RPCs as long as you make a couple changes to ~/Library/Application\ Support/Dogecoin/dogecoin.conf, so I'm using that as a workaround.

[voidref]

Because your user name is awesome, I'll help you out.

use the "ln -s" command to create a symlink

ln -s /path/to/the/static/lib /usr/local/lib

[voidref]

Because your user name is awesome, I'll help you out.

use the "ln -s" command to create a symlink

ln -s /path/to/the/static/lib /usr/local/lib

[bacongobbler]

Thanks @voidref. I understand basic UNIX commands, I'm just not sure in what directory the static libs are built. I'm on my phone, so I'll edit this post later with a directory tree. :)

[bacongobbler]

Thanks @voidref. I understand basic UNIX commands, I'm just not sure in what directory the static libs are built. I'm on my phone, so I'll edit this post later with a directory tree. :)

[voidref]

just search for a bunch of .a files in the boost build output dir.

can always do: mdfind -name libboost_atomic-mt.a to find out where they are.

[voidref]

just search for a bunch of .a files in the boost build output dir.

can always do: mdfind -name libboost_atomic-mt.a to find out where they are.

[bacongobbler]

All right, so I've symlinked the .a files located at ./boost_1_55_0/stage/lib to /usr/local/lib, but compiling dogecoind fails due to some undefined symbols for x86_64. Logs are available at https://gist.github.com/bacongobbler/712a04bfe9884648d41e

[bacongobbler]

All right, so I've symlinked the .a files located at ./boost_1_55_0/stage/lib to /usr/local/lib, but compiling dogecoind fails due to some undefined symbols for x86_64. Logs are available at https://gist.github.com/bacongobbler/712a04bfe9884648d41e

[guysoft]

Hey guys.
I had the exact same problem with current trunk. I tried with Brew and got that. Trying now with macports.

[guysoft]

Hey guys.
I had the exact same problem with current trunk. I tried with Brew and got that. Trying now with macports.

[guysoft]

Hey, so there is documentation on this back in the kittehcoin tracker.
They also have a commit in there so worth looking at linked to that issue, they change compiler flags there specifically for mac.

The only way I found to fix the undefined symbols for x86_64 was to switch to macports, and set
in the .pro file CFLAGS += -stdlib=libstdc++ as explained in this issue on the bitcoin tracker. Furthermore in the bitcoin readme there is more detail on why to use their version of boost (not just "... REASONS" as stated in the current doc, they supply their own mac ports package).

With this new information suggest opening this issue. I hope that's ok.

[guysoft]

Hey, so there is documentation on this back in the kittehcoin tracker.
They also have a commit in there so worth looking at linked to that issue, they change compiler flags there specifically for mac.

The only way I found to fix the undefined symbols for x86_64 was to switch to macports, and set
in the .pro file CFLAGS += -stdlib=libstdc++ as explained in this issue on the bitcoin tracker. Furthermore in the bitcoin readme there is more detail on why to use their version of boost (not just "... REASONS" as stated in the current doc, they supply their own mac ports package).

With this new information suggest opening this issue. I hope that's ok.