0.96.4 RC3 - page 3. | Bitcointalksearch.org

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

Quote from: alomar on January 17, 2018, 10:41:21 AM

"sudo make install" after compiling on my system for my current version. does that mean i did both a compile and a local install? if that's the case, then i need to run "make uninstall" on the previous version before "make clean", right?

Typically you don't need to, as the same files as the previous install will be copied over, overwriting the previous install. But it's preferable to "make uninstall", as it guarantees the old files are removed, in case some of these files are not covered by the new install.

PhoenixFire

member

Activity: 270

Merit: 36

Quote from: alomar on January 17, 2018, 10:41:21 AM

so i compiled my current version and run armory via the CLI by typing "armory" using the /usr/local/bin. thus, i'm running the binaries from the source folder without an install, correct, ? if so, do i just "make clean" before i compile this new version?

edit: wait, i think i ran "sudo make install" after compiling on my system for my current version. does that mean i did both a compile and a local install? if that's the case, then i need to run "make uninstall" on the previous version before "make clean", right?

No to the first paragraph, yes to the second:

make uninstall (sudo if it fails)
make clean
make
make install (sudo if it fails)

alomar

member

Activity: 178

Merit: 10

Quote from: goatpig on January 17, 2018, 04:53:30 AM

"Compile" is to build the binaries. Install is to setup the binaries on your system. If you use my builds you are only installing, if you build from source, you are "compiling" then installing. If you build from source you could also only "compile" and run the binaries from the source folder, without installing.

I put compile in quotes cause the actual term is to build the binaries.

so i compiled my current version and run armory via the CLI by typing "armory" using the /usr/local/bin. thus, i'm running the binaries from the source folder without an install, correct, ? if so, do i just "make clean" before i compile this new version?

edit: wait, i think i ran "sudo make install" after compiling on my system for my current version. does that mean i did both a compile and a local install? if that's the case, then i need to run "make uninstall" on the previous version before "make clean", right?

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

"Compile" is to build the binaries. Install is to setup the binaries on your system. If you use my builds you are only installing, if you build from source, you are "compiling" then installing. If you build from source you could also only "compile" and run the binaries from the source folder, without installing.

I put compile in quotes cause the actual term is to build the binaries.

alomar

member

Activity: 178

Merit: 10

Quote from: goatpig on January 16, 2018, 07:00:16 PM

compile or install?

hmm, what's the difference in this case and which one should i do and why? i want to upgrade to this new version from 0.96.3.991

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

compile or install?

Before you compile you should "make clean". If you install, you should "make uninstall" on the previous version before "make clean".

alomar

member

Activity: 178

Merit: 10

as a housekeeping note, when we compile this new version, armory_0.96.3.992_src.tar.gz, should we be doing anything to the old version first (uninstall)? or just compile over the top of the old version w/o worrying about anything?

TimS

sr. member

Activity: 250

Merit: 253

Soo the problem is solved. I noticed that ArmoryDB.exe (probably from an older version of Armory) was still running. I ended that process, moved log files, and now Armory is working. Thanks for the help.

droark

sr. member

Activity: 525

Merit: 282

satoshi-datadir does need to be D:\Bitcoin\blocks, but anyway, please post your full logs using this particular flag. Thanks.

TimS

sr. member

Activity: 250

Merit: 253

Quote from: droark on January 16, 2018, 01:05:23 AM

Is that the full path where the blockchain resides? It's not in D:\Bitcoin\blocks or something similar?

No, D:\Bitcoin\ is the home directory, and then D:\Bitcoin\blocks\ is where the blockchain resides. I tried it the other way, no change:

Code:

2018-01-16 06:18:41 (INFO) -- ArmoryUtils.pyc:1301 -     satoshiHome     : D:\Bitcoin\blocks
...
2018-01-16 06:18:44 (ERROR) -- BDM.pyc:197 - DB error: C:\Users\[user]\AppData\Roaming/Bitcoin/blocks is not a valid path

droark

sr. member

Activity: 525

Merit: 282

Is that the full path where the blockchain resides? It's not in D:\Bitcoin\blocks or something similar?

TimS

sr. member

Activity: 250

Merit: 253

I started Armory with --satoshi-datadir="D:\Bitcoin" and it's not connecting to my Bitcoin Core node. The log looks like it reads this, but then looks for the DB in the wrong place:

Code:

2018-01-15 22:07:29 (INFO) -- ArmoryUtils.pyc:1301 -     satoshiHome     : D:\Bitcoin
2018-01-15 22:07:32 (ERROR) -- BDM.pyc:197 - DB error: C:\Users\[user]\AppData\Roaming/Bitcoin/blocks is not a valid path

Let me know if I should provide full logs or do something different.

jojo69

legendary

Activity: 3374

Merit: 4738

diamond-handed zealot

awesome, been waiting for this one, grabbing now

idoB

jr. member

Activity: 70

Merit: 2

Verified: the problem with splashscreen freeze that was present in RC2 ('Start in' field in shortcut) is solved in RC3. THANKS!

PhoenixFire

member

Activity: 270

Merit: 36

No problems so far. Thanks, goatpig!

goatpig

legendary

Activity: 3794

Merit: 1375

Armory Developer

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

Test away.

Topic: 0.96.4 RC3 - page 3. (Read 1031 times)