[Installing openssl with Homebrew (see https://brew.sh) fixed it!]

Just an announcement in case anybody else has the same problem:

I just installed Armory on a relatively new Mac (running OS X Mojave, not the brand new Catalina).  Armory did not work, it could not open the app.  Starting the relevant script inside the Armory.app folder showed that the error was that a library in /usr/local/opt/openssl/lib could not be opened, that folder was missing.

Installing openssl with Homebrew (see https://brew.sh) fixed it!

It seems to be an error in building the MacOS executable, where OpenSSL has not been bundled as it should have been.

Hi,

I have previously built Armory for the Raspberry Pi using the instructions on the git.  I think it was version 0.93.3.  Now I need 0.96.2 so I can get my BCH out of the wallet, and I would prefer not to export private keys as I plan on keeping by BTC there (making a new Armory wallet is easy - getting the 3-of-5 backup distributed requires some logistics. )

Anyway, I compiled on an up-to-date lubuntu with the RPi cross compiler (comes as a package).  Moved it to a newly installed RPi.  If I use a Raspbian based on Debian Jessie then there is a GLIBC version mismatch, using the just released Raspbian based on Stretch does not have this problem.  But as Armory starts up, it crashes (before the splash screen) with an "Illegal instruction".

My RPi is really old, it was the first (or maybe second) model, and has a version 7 ARM cpu.  I tried recompiling with -march=armv7, but that did not help.  Does Armory contain some assembler code or the like that depends on a newer ARM CPU, or does a modern GCC just generate too new code?

I guess I could buy a new RPi.  Or does anyone else have a suggestion.

I just want to report that the latest version 0.92.2 builds without problems on a Mac.  I followed the instructions on https://github.com/goatpig/BitcoinArmory/blob/master/osxbuild/OSX_build_notes.md almost to the letter.

Comments:

* I have previously problems building Armory due to other stuff installed on my machine with Homebrew.  I recommend building on a clean (virtual) machine.

* I used a virtual machine with Max OS 10.11 "El Capitan", as recommended by the developers.

* You do not need the full Xcode 7.3.1.  From the Apple developer pages, download instead "Command Line Tools for Xcode 7.3.1".  That will save you from a 5GB+ download and a similar installation.

* You need to get the source code with git.  And remember after checking it out, you must run

Code:

git submodule init
git submodule update

Failure to do this will silently fail, the app cannot start.

* El Capitan is the last version of Mac OS which works in a VM (with the possible exception of early releases of Sierra).  An up-to-date Sierra discovers that it is in a VM, and refuses to boot.

* Xcode 8 (for Sierra) reportedly build apps that only work with Sierra, regardless of the settings in Xcode.  This may not apply to Armory which is built from the command line.

I transferred the resulting App to my laptop running macOS Sierra - It looks like it is working, although I have not tested it extensively.

[Does anyone know how to do this?]

Hi,

I am trying to run both the BTC and the BCH chain on my Mac.  My plan is

1) Have both Bitcoin Core and Bitcoin Unlimited (cash edition) running on my mac.  The block chain is on an external harddisk, with softlinks from ~/Library/Application Support/Bitcoin/blocks to the relevant folder on my external disk.  This works fine with Bitcoin Core.  

On that disk, I created a new folder for the BCH chain where I softlinked hardlinked all block files but the last one (which I copied), I did this on the 1st August.  So I should have a secondary chain for BCH.  Now I want Bitcoin Unlimited to use this secondary block chain, that requires making it use another folder than ~/Library/.../Bitcoin for the configuration file and everything else.  Does anyone know how to do this?

2) I also need two versions of the Armory app.  Command line arguments do not really work on a Mac, so I imagine making a new ArmoryCash.app folder, softlink everything from the Armory.app folder into that one except the startup script, where I can add command line arguments to use the Bitcoin Cash folder (and an alternate Armory data folder as well).  Does this sound reasonable?

I could of course also run the BCH chain on a different machine, but that would be very inconvenient.

[appreciate very much]

Hi goatpig,

I am using the the lastest release-candidate for 0.96 on my Macbook, since there is no macOS build on 0.96.  As I understand it, some problem caused you to delay releasing a macOS version.  Was that problem introduced after the last pre-release, or is my version also susceptible to some macOS related bug?  In the latter case, am I better off trying to build from source myself, and get the benefits of whatever other bug fixes you have introduced in the final release?

I only use Armory sporadically and have not noticed anything bad happening.

Finally, let me say that I appreciate very much that you are making the effort of maintaining Armory also for macOS, although I am pretty sure that is a pain in the butt.  Thanks!  For a while I had to use a Virtual machine with Linux to get it to run, that was doable but really not as practical

Hi,

Thanks for the new Armory version.  I am patiently waiting for the OS X version while still running the latest pre-release.   

I have a question about the new output script types available in the newest Armory.  Do I understand it correctly that it is when I generate an address to receive bitcoins that I select the type?

If so, I assume the new types generate different bitcoin addresses based on the same(?) underlying private key (I am here assuming that Armory still generates a single chain of private keys.  I guess that cannot have changed if it is still sufficient to back the old wallet file up). 

Are the new ways of generating bitcoin addresses Armory-specific, or are they standardized?  I am asking because who knows what will happen to the Armory project in the future.  At some point it may be discontinued, or the blockchain may become so big that I can no longer run Bitcoin Core.  It gives me peace of mind that I can always run Armory in a tiny virtual environment and extract the private keys to another wallet.  But that of course requires that the other wallet can generate the same kinds of output.

Hi,

I have been running bitcoind and Armory in a virtual linux box for a while, but for various reasons wanted to move back to running natively on my MacBook.

I started Armory with a completely empty ~/Library/Application Suppport/Armory directory except for the wallet files, and with BitcoinQT running and up to date.  Armory got stuck while ArmoryDB was scaning the TX's (I think it said).  Killing everything, and restarting, Armory is working fine, can both send and receive bitcoins.

But whenever I quit Armory, the ArmoryDB process keeps running.  I have to kill it manually to start Armory again.  Also, when Armory exits, the Mac pops up a window claiming it crashed, and offering to restart it.

It is not a serious problem, only a nuisance.  But for new users it could be problematic.

Log files:
armorycpplog.txt: http://pastebin.com/jXdvm88C
armorylog.txt: http://pastebin.com/fvm61ZGU
dbLog.txt: http://pastebin.com/e1MZjHBu