Yesterday So maybe i did missed your updated versions...Ill try again

I finally was able to build Armory on my Raspberry Pi.

First I was met with the error described in this thread.


Turns out that cryptopp 5.6.1 (which is included with Armory) has a bug in its Makefile that makes it detect the compiler on a Raspberry Pi as a CC Sun C++ compiler (I have no idea why that happens, but that's what seems to happen). Replacing the Makefile in cppForSwig/cryptopp with the GNUmakefile from cryptopp 5.6.2 fixes this issue.

Next I was getting strange assembler errors from g++ like:


and


and it turns out this was caused by the Pi running out of memory. Creating a 500 MB file in my home dir and mounting it as swap fixed that issue, as described here: http://www.roberteklund.org/projects/raspberry-pi#TOC-Installation1

But now that I try to run Armory, I get the following error. Not sure how to deal with that.

Then what happens with my wallet?

It seems to return the correct value for platform.system() at least.


And putting in the "raise" as you say makes Armory start properly. Yay!

I see what's going on.  It fails to set the CpuStr variable because platform.processor() is empty.  I forgot to set a default value.  I guess that will be fixed in the next release. 

Good to know about the CPU "model name".  Oh well.  I really don't need it, I just need to add a default value for that completely informational-not-functional piece of code...

I didn't realize there was a new release of Crypto++ recently.  I will look into it.  There was a bug in the old version that I had to manually fix, but it was so long ago, I don't remember what it was.  I may have to do some git-blaming to figure it out.

Honestly, I was hoping to just eventually release an offline bundle for the RPi.  But I'm not sure if I can support that at this time.  I finally have an RPi, but I haven't really had time to set it up.  Maybe someone could help me figure out what is needed for the offline bundle...?  (and a good way to set it up, like what image to install, etc)

Ok, my problem has been resolved per your instructions. I had to perform an uninstall first and not just a reinstall.  I also like the way it loads the bitcoind daemon for me now. I don't have to run a separate program. Thanks.

Ack, that's quite a long compile time!  I didn't realize that it couldn't be compiled in the available RPi RAM.  You have A or B pi?   I guess I'll download the Raspbian image and take a shot at it... in a little bit.  At the moment, I gotta focus on some other development activities. 

For the unlocking, there's not much you can do about it.  Armory does a bunch of verification checks when unlocking to make sure there's no corruption.  Although it takes a while, it's saved my bacon in a couple instances (and for other users) when it did actually find something was corrupted.  This will prevent you from using a corrupted wallet and potentially using addresses that were based on a faulty chain calculation. The downside is that there's a lot of EC-multiply operations being performed when you unlock, which does take a while, especially on slower HW.

I suppose you could run with a much smaller keypool on the offline computer, since it doesn't need any lookahead  (because it's not looking anywhere for transactions).  That would speed up unlocking in the short-term.

I would highly recommend following the guide here to get a cross-compiler set up for the Pi. Compiling on the Pi itself seems like a form of masochism.

I've been trying to test the cold wallet functionality with a small 0.01 btc transfer, but it keeps not allowing me to send btc to the cold wallet without a fee. I thought if I waited a few days it would work since then there'd be over 120 confirmations on my recently transferred BTC, but it still isn't working. I tried up to 0.06 btc, but it's still not allowing without the transaction fee. The regular bitcoin client allowed me to send both 0.01 btc and 0.05 btc to my armory wallet without any fees. Not sure what the issue is?