Didnt get it running either.
I just went back to Armory 0.93.3 and Qt 13.2. That works fine, although takes up a heck of a lot of space and it's probably missing a bunch of functionality that I don't need.
Topic: Armory on macOS (Read 859 times)
I just went back to Armory 0.93.3 and Qt 13.2. That works fine, although takes up a heck of a lot of space and it's probably missing a bunch of functionality that I don't need.
Didnt get it running either.
I am running 0.96 with Core 14.1. I have not seen any problems, but then I have only made two transactions since I upgraded to these versions.
macOS Sierra 10.12.5
Edit: NOT 0.96 of course. The latest prerelease, 0.95.99.3-beta
macOS Sierra 10.12.5
Edit: NOT 0.96 of course. The latest prerelease, 0.95.99.3-beta
Actually scratch that, I wasn't able to get 0.95.1 working. This was a build provided from the Github release page.
I got a database error once it was up and running, it's looking for the blocks folder from the Bitcoin-Qt sync, but that's symlinked from the default folder in ~/Library/Application Support/Bitcoin/ to an external hard drive and it seems to have issues with that for whatever reason. I can't move the blockchain because my main drive doesn't have anywhere near the space for it. I think this has been discussed here: https://bitcointalksearch.org/topic/m.17047649 but I'm not able to build Armory from source easily on Sierra, in spite of the instructions provided, and don't have the time to debug it unfortunately.
@gangtraet, would you be willing to create a build of 0.95.99 that I could try (particularly if I could ask you to make the edits to the source suggested in the link above). Aware of the risks if I'm not the one building it. Many thanks
.
I am running 0.96 with Core 14.1. I have not seen any problems, but then I have only made two transactions since I upgraded to these versions.
macOS Sierra 10.12.5
Edit: NOT 0.96 of course. The latest prerelease, 0.95.99.3-beta
macOS Sierra 10.12.5
Edit: NOT 0.96 of course. The latest prerelease, 0.95.99.3-beta
Thanks, I will give it a try!
Is there any version of Armory still running with Sierra 10.12.4 ?
0.93.3 and 0.95.1 wont start up for me.
0.93.3 and 0.95.1 wont start up for me.
@MishaMuc, I think I was able to get 0.95.1 working once I had installed some of the relevant Python library dependencies using homebrew (I can't remember the exact post, but it is listed in one of the earlier release threads). Try to run the Armory executable directly from the shell to see the error output as it crashes out, that'll tell you what libraries are missing.
Also 0.95.1 does not work with 0.14.x of Bitcoin Core I think, so you'll need to use the old client.
Hoping for a 0.96.1 release sooner rather than later
.
Is there any version of Armory still running with Sierra 10.12.4 ?
0.93.3 and 0.95.1 wont start up for me.
0.93.3 and 0.95.1 wont start up for me.
Thanks for your reply. I will let it wait. But just one more observation, that may help you:
I copied ArmoryQt.py into the app, then I get this error about incompatible library version:
It looks like Armory picks up a version of libpng that I have installed with brew (needed by other software). The version inside Armory.app is also libpng16.16.dylib, though.
I will let this rest until 0.96.1 goes officially into testing on macOS.
I copied ArmoryQt.py into the app, then I get this error about incompatible library version:
Code:
16:07 workspace$ Armory.app/Contents/MacOS/Armory
Traceback (most recent call last):
File "/Users/******/development/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/py/usr/local/lib/armory/ArmoryQt.py", line 37, in
from PyQt4.QtGui import *
ImportError: dlopen(/Users/******/development/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PyQt4/QtGui.so, 2): Library not loaded: /usr/local/opt/libpng/lib/libpng16.16.dylib
Referenced from: /Users/******/development/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/Frameworks/QtGui.framework/Versions/4/QtGui
Reason: Incompatible library version: QtGui requires version 46.0.0 or later, but libpng16.16.dylib provides version 45.0.0
I will let this rest until 0.96.1 goes officially into testing on macOS.
It will get attention once 0.96.1 is in testing
Had to get rid of twisted/openssl first. If you want to build from source, try the current state of the testing branch.
I tried that. It compiled without problems, but does not run. When I click the app, nothing happens, and the log files are not touched. I tried running it from the command line:
Code:
15:15 workspace$ Armory.app/Contents/MacOS/Armory
/Users/*****/development/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/Python: can't open file '/Users/*****/development/BitcoinArmory/osxbuild/workspace/Armory.app/Contents/MacOS/py/usr/local/lib/armory/ArmoryQt.py': [Errno 2] No such file or directory
15:15 workspace$ ls -l Armory.app/Contents/MacOS/py/usr/local/lib/armory/
total 128
-rwxr-xr-x 1 ***** staff 64488 May 11 15:11 ArmoryMac.so
It looks like the Python code was not installed properly. The file ArmoryQt.py is not mentioned in the log.
Code:
15:21 osxbuild$ grep ArmoryQt build-app.log.txt
15:21 osxbuild$ ls -lh build-app.log.txt
-rw-r--r-- 1 ****** staff 7.0M May 11 15:11 build-app.log.txt
Had to get rid of twisted/openssl first. If you want to build from source, try the current state of the testing branch.
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
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
Jump to: