I thought it would be a good idea to upgrade my offline signer to a current version. But I had to build from source because I need a 32bit executable (old Pentium M)
Compilation on 32bit x86 showed an error which was already reported for 0.95 - but the OP failed to respond to Goatpig's question about the build environment.
Check my response in that thread https://bitcointalksearch.org/topic/m.20477795 if you run into compile error on "non standard" hardware.
Topic: Armory 0.96.1 is out! - page 3. (Read 6699 times)
pull out my offline signer
You get some major hip points for that right there!
noob here,
can somebody here help me? or steer me to a forum that can? I upgraded to bitcoincore 0.14.2 and armory 0.96 on a WIN7x64 pc (acts as a file server so its never off)..
before I upgraded I received a couple payments to my armory wallet no problem, but after i upgraded and 3 days for armory to finaly load I have received several payments,
but all payments I have received are unconfirmed - NOT spendable..
I have not tried the "-rescan" yet as it took so long for armory to load in the first place
can somebody here help me? or steer me to a forum that can? I upgraded to bitcoincore 0.14.2 and armory 0.96 on a WIN7x64 pc (acts as a file server so its never off)..
before I upgraded I received a couple payments to my armory wallet no problem, but after i upgraded and 3 days for armory to finaly load I have received several payments,
but all payments I have received are unconfirmed - NOT spendable..
I have not tried the "-rescan" yet as it took so long for armory to load in the first place
i'm getting this in Debian Jessie:
how do i upgrade to ">= 5.2"? is that GCC?
Code:
debian@debian:~/Downloads$ sudo dpkg -i armory_0.96.1_amd64.deb
(Reading database ... 129820 files and directories currently installed.)
Preparing to unpack armory_0.96.1_amd64.deb ...
Unpacking armory (0.96.1-1) over (0.96.1-1) ...
dpkg: dependency problems prevent configuration of armory:
armory depends on libstdc++6 (>= 5.2); however:
Version of libstdc++6:amd64 on system is 4.9.2-10.
dpkg: error processing package armory (--install):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for mime-support (3.58) ...
Errors were encountered while processing:
armory
debian@debian:~/Downloads$
how do i upgrade to ">= 5.2"? is that GCC?
Jessie is GCC 4.9, I build on Ubuntu 16.04, which is GCC 5.4.
You would need a build with an earlier version of GCC, which I'll add with the offline builds for 0.96.2. For now, you'll have to build from source, which is fairly easy on Jessie.
Updating 0.96 to 0.96.1 on Ubuntu 16.04 (by installing provided .deb package) made the graphical icons for Armory disappear. Still able to start Armory by command line, though.
Will look into it
I can confirm that with your libpng commit https://github.com/goatpig/BitcoinArmory/pull/273/commits/1f4d8d365ad5d91032e57a84d14bbb2e123483d8 fix, things build successfully on macOS! Feel free to merge this into master, goatpig.
Done, will be part of 0.96.2. And yes, I had to cherry pick a commit from testing back into master after I tagged cause I forgot to grab OS build fix PR like an idiot. I wasn't gonna retag cause it's a hassle to pull out my offline signer, and I'm doing a .2 in a couple weeks anyways.
How was the OSX build actually built? Was it actually built on the v0.96.1 tag or not? I ask because one commit after the v0.96.1 tag on the master branch, there is a "Fix OSX build" commit. Was the OSX build actually done on that separate commit?
Yes. It wouldn't build with the 0.96.1 tag (oversight by goatpig), so the fix from testing was copied over. That fixed everything, although the build process is broken again due to the libpng library version in the script being unavailable now. (Sourceforge just deleted that version.) I'll PR a new script in a bit.
I can confirm that with your libpng commit https://github.com/goatpig/BitcoinArmory/pull/273/commits/1f4d8d365ad5d91032e57a84d14bbb2e123483d8 fix, things build successfully on macOS! Feel free to merge this into master, goatpig.
Updating 0.96 to 0.96.1 on Ubuntu 16.04 (by installing provided .deb package) made the graphical icons for Armory disappear. Still able to start Armory by command line, though.
i'm getting this in Debian Jessie:
how do i upgrade to ">= 5.2"? is that GCC?
Code:
debian@debian:~/Downloads$ sudo dpkg -i armory_0.96.1_amd64.deb
(Reading database ... 129820 files and directories currently installed.)
Preparing to unpack armory_0.96.1_amd64.deb ...
Unpacking armory (0.96.1-1) over (0.96.1-1) ...
dpkg: dependency problems prevent configuration of armory:
armory depends on libstdc++6 (>= 5.2); however:
Version of libstdc++6:amd64 on system is 4.9.2-10.
dpkg: error processing package armory (--install):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for mime-support (3.58) ...
Errors were encountered while processing:
armory
debian@debian:~/Downloads$
how do i upgrade to ">= 5.2"? is that GCC?
How was the OSX build actually built? Was it actually built on the v0.96.1 tag or not? I ask because one commit after the v0.96.1 tag on the master branch, there is a "Fix OSX build" commit. Was the OSX build actually done on that separate commit?
Yes. It wouldn't build with the 0.96.1 tag (oversight by goatpig), so the fix from testing was copied over. That fixed everything, although the build process is broken again due to the libpng library version in the script being unavailable now. (Sourceforge just deleted that version.) I'll PR a new script in a bit.
How was the OSX build actually built? Was it actually built on the v0.96.1 tag or not? I ask because one commit after the v0.96.1 tag on the master branch, there is a "Fix OSX build" commit. Was the OSX build actually done on that separate commit?
Builds available on the Github release page, as usual:
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.1
Changelog (https://github.com/goatpig/BitcoinArmory/blob/v0.96.1/changelog.txt):
Note:
0.96.2 is in tow with lots of DB fixes and improvements and offline builds.
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.1
Changelog (https://github.com/goatpig/BitcoinArmory/blob/v0.96.1/changelog.txt):
Quote
== Added ==
- Raised default fee to 200 satoshi/Bytes. This fee will apply when using defaults and the node RPC is down.
Any applied fee lower than that rate will trigger a warning message box. Users have to actively choose to
bypass the warning.
- Split unit tests building from default autotools setup. To build tests, use:
./configure --enable-tests.
- You can now disable GUI in the autotools build system. Use:
./configure --without-gui
- When spawned with a cookie file, the DB now randomizes its listen port to (49150 + [0-15000]) and reports it in the cookie file.
- Added --fcgi-port command line argument to the DB
- Address comments are now visible again in the Coin Control GUI
- DB messages now have checksums; this improves error and version mismatch detection
- Transactions that failed to broadcast throug the P2P layer will now be pushed to the RPC afterwards, if it's enabled
- Refresh address view in Wallet Properties dialog on several user interactions.
- RPC status is now signaled in the bottom right corner status bar. Disabled RPC will result in bold purple text.
- Highly improved DB corruption self diagnosis and automated fixing.
- Zero confirmation parser pool now is now capped at 100 threads.
You can modify this value with the --zcthread-pool command line argument.
== Fixed ==
- ZC parsing will no longer occur while the BDM is initializing
- Wait on cookie file creation before connecting to auto managed DB
- Fixed registration/callback premature garbage collection
- Translation patch issues
- Fixed "Fund from wallet" lockbox GUI
- Fixed TxIn/Out pretty printing
- Tied init phase spinning icon rotation to progress notifications. The icon will not spin when no progress data is received, correctly
indicating the DB is hanging.
- Fixed cryptopp build against older CPUs (no AES or PCLMUL archs).
- Fixed RBF bumping with no change.
- Improved timestamps granularity in logs.
- Improved transaction broadcast consistency.
- Improved error message verbose of timed out transaction broadcasts.
- ./configure --prefix now propagates correctly to Makefiles.
- Fixed several memleaks in the database code.
- Fixed false positive throws over bad packet detection in socketing layer.
- Fixed coin selection edge cases.
- Fixed the displaying of address comments in the lobby ledger.
== Removed ==
- Python-twisted dependency. This should remove the underlying openSSL dependency as well.
- Database command prompt will no longer appear when auto managing the DB on Windows
- Raised default fee to 200 satoshi/Bytes. This fee will apply when using defaults and the node RPC is down.
Any applied fee lower than that rate will trigger a warning message box. Users have to actively choose to
bypass the warning.
- Split unit tests building from default autotools setup. To build tests, use:
./configure --enable-tests.
- You can now disable GUI in the autotools build system. Use:
./configure --without-gui
- When spawned with a cookie file, the DB now randomizes its listen port to (49150 + [0-15000]) and reports it in the cookie file.
- Added --fcgi-port command line argument to the DB
- Address comments are now visible again in the Coin Control GUI
- DB messages now have checksums; this improves error and version mismatch detection
- Transactions that failed to broadcast throug the P2P layer will now be pushed to the RPC afterwards, if it's enabled
- Refresh address view in Wallet Properties dialog on several user interactions.
- RPC status is now signaled in the bottom right corner status bar. Disabled RPC will result in bold purple text.
- Highly improved DB corruption self diagnosis and automated fixing.
- Zero confirmation parser pool now is now capped at 100 threads.
You can modify this value with the --zcthread-pool command line argument.
== Fixed ==
- ZC parsing will no longer occur while the BDM is initializing
- Wait on cookie file creation before connecting to auto managed DB
- Fixed registration/callback premature garbage collection
- Translation patch issues
- Fixed "Fund from wallet" lockbox GUI
- Fixed TxIn/Out pretty printing
- Tied init phase spinning icon rotation to progress notifications. The icon will not spin when no progress data is received, correctly
indicating the DB is hanging.
- Fixed cryptopp build against older CPUs (no AES or PCLMUL archs).
- Fixed RBF bumping with no change.
- Improved timestamps granularity in logs.
- Improved transaction broadcast consistency.
- Improved error message verbose of timed out transaction broadcasts.
- ./configure --prefix now propagates correctly to Makefiles.
- Fixed several memleaks in the database code.
- Fixed false positive throws over bad packet detection in socketing layer.
- Fixed coin selection edge cases.
- Fixed the displaying of address comments in the lobby ledger.
== Removed ==
- Python-twisted dependency. This should remove the underlying openSSL dependency as well.
- Database command prompt will no longer appear when auto managing the DB on Windows
Note:
0.96.2 is in tow with lots of DB fixes and improvements and offline builds.
Jump to: