Open akaihola opened 10 years ago
Can you do me a huge favor and try doing this on the "testing" branch? We attempted to fix this issue in the Makefile, and I think we did. I want to make sure it works for you. I might merge this into 0.88.1 if that's the case... or maybe I just get the new version out soon!
Work-around: in cppForSwig/Makefile
, replace this
STATICPYTHON += "$(DEPSDIR)/lib/libpython$(PYVER).a"
with this:
STATICPYTHON += "$(DEPSDIR)/lib/i386-linux-gnu/libpython$(PYVER).a"
@etotheipi Absolutely, I'll do that tonight on my home laptop on 13.10.
I also tried the same now on an Ubuntu 13.04 box with exactly the same result on the master
branch. On the testing
branch it does work perfectly.
I'm looking forward to the next version, so I'm glad to be able to help!
(I was actually wondering where the source code for the upcoming version lives – the testing
branch isn't mentioned on bitcoinarmory.com. Actually, besides the git clone
command line, I couldn't even find any link to this GitHub repo or the issue tracker in the "Developers" section. Do you omit this information from the website on purpose?)
@etotheipi Building the testing
branch succeeds on Xubuntu 13.10. However, Armory won't run (see #120). Edit: It does run, still looking for the cause of the failed compilation.
On my Ubuntu 13.04 box it both compiles and runs perfectly.
On Xubuntu 13.10, I did:
The Git HEAD was pointing to 09988e90995b837450ca624bebf9c7e7f832d846
Make failed at this point:
My system does have
libpython2.7.a
at the following locations: