Pages:
Author

Topic: 0.96.1 testing build #4 - page 9. (Read 8012 times)

ask
legendary
Activity: 1386
Merit: 1004
May 15, 2017, 02:54:36 PM
#3
Now works fine. Thank you!
brand new
Activity: 0
Merit: 0
May 14, 2017, 06:21:25 PM
#2
Nice my problem with having to restart Armory twice is fixed with this build thank you.
Just my offline Netbook has the mentioned unkown instruction problem but well that thing can wait.
member
Activity: 96
Merit: 10
May 15, 2017, 06:24:27 AM
#2
I'm going to test again encrypting my HDD, but this time I'll use AES 128bit instead of 256bit... maybe this was too heavy in the first place.
legendary
Activity: 3640
Merit: 1345
Armory Developer
May 14, 2017, 05:32:57 PM
#1
Third testing builds are out.

------------------

Binaries:
https://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.0.4

Fixes/Changes:

Code:
v0.96.1

== Added ==
   - 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.

== Fixed ==
   - ZC parsing will no long occur while the BDM is initializing
   - Wait on cookie file creation before connection 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

== Removed ==
   - Python-twisted dependency. This should remove the underlying openSSL dependency as well.

--------------

Linux users:

If the build fails to run on your setup (unknown instructions), it means your CPU is missing SSE4/AES/PCLMUL instructions. There will be a fail safe gcc4.7 build without any of those instructions for the actual release, but for the testing phase, you'll want to build the code directly on your machine. The build process has been fixed so you should have an easy time with it.

--------------

OSX users:

Added a build for this version.
Pages:
Jump to: