Any pointers on how to install Pygame and PIL on ubuntu/debian, or is that just for Windows, and I should just keep using /graphs/?
I used apt. Pretty sure it was just 'sudo apt-get install python-pygame python-image' but it might be python-imaging. I half remember it not being python-pil (which would have been too easy). Use /static/ though. I don't think it needs either of those since it is all html/css/javascript |
|
|
|
Odd that you were charged a fee like that; I wonder why. I think Red Emerald is right, it probably hadn't even been 126 confirmations. Like I said, I assumed that the 120 required before they could be spent made them old enough. It's also possible that the minimum BTC amount to not require a fee is higher, but I think that depends on age, seems like I saw the formula about what causes a fee to be required once, just kinda forgot about it. |
|
|
|
I just spent coins from a generate and was charged a fee. The generate was for .6793514 and since 120 confirmations were required before they could be spent, and since I was trying ot send exactly .6793514, I expected to be able to send the transaction for free. Instead, a fee of .0005 was required and I had to spend .6788514 instead to afford the fee. I know that ultimately fees will be necessary to support mining, but I believe right now fees are only required for transactions that fall outside of a certain scope. My expectation did involve some assumption, but was based on this (from FAQ): Why is there a minimum payout?
This feature was added to help miners avoid transaction fees. Just out of curiosity, was the minimum payout's intent to be able to spend without a fee (in which case maybe it is currently too low, whether it was when implemented or not) or just to minimize fees (100 .00678851 inputs would have presumably required a larger fee)? IIRC once the coins are 120 generations in, they count as new coins. Since they are new coins, they don't get to be spent for free. I think you could have waited for the coins to mature more and saved yourself about 2 cents. priority = sum(input_value_in_base_units * input_age)/size_in_bytes
No clue what your size_in_bytes is or how to tell though. |
|
|
|
My point is that in time he won't be earning 3-4 BTC per month he will be getting 0.1 BTC per month "for free" and paying 20 BTC in electricity to get it. Mining to educate about Bitcoins. I don't care if they pay too much electricity at first, they'll learn by themselves and they will take a decision accordingly. But at that point, they'll know what Bitcoin is, they will probably have a couple of Bitcoins and they will continue to read and learn by themselves. The biggest obstacle for Bitcoin is having a wallet with 0 BTC. CPU mining used to be a great way to get involved in Bitcoin. The vast majority of miners (including me) came in too late for CPU mining to be worth it. I think the wasted electricity does matter. I wish bitcoin could survive without needing such environmentally expensive proof-of-work. If your grandma just want a few bitcents to learn, thats what the bitcoin faucet is for. Or how about you sell your grandma coins that you mined. IMO getting a mining rig running at grandma's house is not going to launch bitcoin into mainstream. |
|
|
|
Just wondering, is there a way to have a bash script run at start up?
Same way you run a bash script at start up on any other linux machine. BAMT is just debian with the mining stuff installed. Write an init script or just add a line to /etc/rc.local |
|
|
|
Is there anyone that has tried to open a p2pool node through the Tor network ?
Is it possible? Can miners connect to a tor hidden service?
7nnukfynqh6xqwky.onion:8336  |
|
|
|
I sent some more coins to my offline wallet, and at the same time sent you a small donation |
|
|
|
Files with the .a extension means statically linked. I have been thinking about doing that to avoid these problems in the future, but haven't done it yet. Until then, the project is setup to use the -l options, which requires a .so or .dylib.
You can do a 'find . | grep crypto' from any directory to search the entire subdir tree for a file with that name.
Well that would be a problem. I ran the find command from my homebrew folder. $ find . | grep crypto
./Cellar/cryptopp
./Cellar/cryptopp/5.6.1
./Cellar/cryptopp/5.6.1/include
./Cellar/cryptopp/5.6.1/include/cryptopp
./Cellar/cryptopp/5.6.1/include/cryptopp/3way.h
./Cellar/cryptopp/5.6.1/include/cryptopp/adler32.h
./Cellar/cryptopp/5.6.1/include/cryptopp/aes.h
./Cellar/cryptopp/5.6.1/include/cryptopp/algebra.h
./Cellar/cryptopp/5.6.1/include/cryptopp/algparam.h
./Cellar/cryptopp/5.6.1/include/cryptopp/arc4.h
./Cellar/cryptopp/5.6.1/include/cryptopp/argnames.h
./Cellar/cryptopp/5.6.1/include/cryptopp/asn.h
./Cellar/cryptopp/5.6.1/include/cryptopp/authenc.h
./Cellar/cryptopp/5.6.1/include/cryptopp/base32.h
./Cellar/cryptopp/5.6.1/include/cryptopp/base64.h
./Cellar/cryptopp/5.6.1/include/cryptopp/basecode.h
./Cellar/cryptopp/5.6.1/include/cryptopp/bench.h
./Cellar/cryptopp/5.6.1/include/cryptopp/blowfish.h
./Cellar/cryptopp/5.6.1/include/cryptopp/blumshub.h
./Cellar/cryptopp/5.6.1/include/cryptopp/camellia.h
./Cellar/cryptopp/5.6.1/include/cryptopp/cast.h
./Cellar/cryptopp/5.6.1/include/cryptopp/cbcmac.h
./Cellar/cryptopp/5.6.1/include/cryptopp/ccm.h
./Cellar/cryptopp/5.6.1/include/cryptopp/channels.h
./Cellar/cryptopp/5.6.1/include/cryptopp/cmac.h
./Cellar/cryptopp/5.6.1/include/cryptopp/config.h
./Cellar/cryptopp/5.6.1/include/cryptopp/cpu.h
./Cellar/cryptopp/5.6.1/include/cryptopp/crc.h
./Cellar/cryptopp/5.6.1/include/cryptopp/cryptlib.h
./Cellar/cryptopp/5.6.1/include/cryptopp/default.h
./Cellar/cryptopp/5.6.1/include/cryptopp/des.h
./Cellar/cryptopp/5.6.1/include/cryptopp/dh.h
./Cellar/cryptopp/5.6.1/include/cryptopp/dh2.h
./Cellar/cryptopp/5.6.1/include/cryptopp/dll.h
./Cellar/cryptopp/5.6.1/include/cryptopp/dmac.h
./Cellar/cryptopp/5.6.1/include/cryptopp/dsa.h
./Cellar/cryptopp/5.6.1/include/cryptopp/eax.h
./Cellar/cryptopp/5.6.1/include/cryptopp/ec2n.h
./Cellar/cryptopp/5.6.1/include/cryptopp/eccrypto.h
./Cellar/cryptopp/5.6.1/include/cryptopp/ecp.h
./Cellar/cryptopp/5.6.1/include/cryptopp/elgamal.h
./Cellar/cryptopp/5.6.1/include/cryptopp/emsa2.h
./Cellar/cryptopp/5.6.1/include/cryptopp/eprecomp.h
./Cellar/cryptopp/5.6.1/include/cryptopp/esign.h
./Cellar/cryptopp/5.6.1/include/cryptopp/factory.h
./Cellar/cryptopp/5.6.1/include/cryptopp/files.h
./Cellar/cryptopp/5.6.1/include/cryptopp/filters.h
./Cellar/cryptopp/5.6.1/include/cryptopp/fips140.h
./Cellar/cryptopp/5.6.1/include/cryptopp/fltrimpl.h
./Cellar/cryptopp/5.6.1/include/cryptopp/gcm.h
./Cellar/cryptopp/5.6.1/include/cryptopp/gf256.h
./Cellar/cryptopp/5.6.1/include/cryptopp/gf2_32.h
./Cellar/cryptopp/5.6.1/include/cryptopp/gf2n.h
./Cellar/cryptopp/5.6.1/include/cryptopp/gfpcrypt.h
./Cellar/cryptopp/5.6.1/include/cryptopp/gost.h
./Cellar/cryptopp/5.6.1/include/cryptopp/gzip.h
./Cellar/cryptopp/5.6.1/include/cryptopp/hex.h
./Cellar/cryptopp/5.6.1/include/cryptopp/hmac.h
./Cellar/cryptopp/5.6.1/include/cryptopp/hrtimer.h
./Cellar/cryptopp/5.6.1/include/cryptopp/ida.h
./Cellar/cryptopp/5.6.1/include/cryptopp/idea.h
./Cellar/cryptopp/5.6.1/include/cryptopp/integer.h
./Cellar/cryptopp/5.6.1/include/cryptopp/iterhash.h
./Cellar/cryptopp/5.6.1/include/cryptopp/lubyrack.h
./Cellar/cryptopp/5.6.1/include/cryptopp/luc.h
./Cellar/cryptopp/5.6.1/include/cryptopp/mars.h
./Cellar/cryptopp/5.6.1/include/cryptopp/md2.h
./Cellar/cryptopp/5.6.1/include/cryptopp/md4.h
./Cellar/cryptopp/5.6.1/include/cryptopp/md5.h
./Cellar/cryptopp/5.6.1/include/cryptopp/mdc.h
./Cellar/cryptopp/5.6.1/include/cryptopp/misc.h
./Cellar/cryptopp/5.6.1/include/cryptopp/modarith.h
./Cellar/cryptopp/5.6.1/include/cryptopp/modes.h
./Cellar/cryptopp/5.6.1/include/cryptopp/modexppc.h
./Cellar/cryptopp/5.6.1/include/cryptopp/mqueue.h
./Cellar/cryptopp/5.6.1/include/cryptopp/mqv.h
./Cellar/cryptopp/5.6.1/include/cryptopp/nbtheory.h
./Cellar/cryptopp/5.6.1/include/cryptopp/network.h
./Cellar/cryptopp/5.6.1/include/cryptopp/nr.h
./Cellar/cryptopp/5.6.1/include/cryptopp/oaep.h
./Cellar/cryptopp/5.6.1/include/cryptopp/oids.h
./Cellar/cryptopp/5.6.1/include/cryptopp/osrng.h
./Cellar/cryptopp/5.6.1/include/cryptopp/panama.h
./Cellar/cryptopp/5.6.1/include/cryptopp/pch.h
./Cellar/cryptopp/5.6.1/include/cryptopp/pkcspad.h
./Cellar/cryptopp/5.6.1/include/cryptopp/polynomi.h
./Cellar/cryptopp/5.6.1/include/cryptopp/pssr.h
./Cellar/cryptopp/5.6.1/include/cryptopp/pubkey.h
./Cellar/cryptopp/5.6.1/include/cryptopp/pwdbased.h
./Cellar/cryptopp/5.6.1/include/cryptopp/queue.h
./Cellar/cryptopp/5.6.1/include/cryptopp/rabin.h
./Cellar/cryptopp/5.6.1/include/cryptopp/randpool.h
./Cellar/cryptopp/5.6.1/include/cryptopp/rc2.h
./Cellar/cryptopp/5.6.1/include/cryptopp/rc5.h
./Cellar/cryptopp/5.6.1/include/cryptopp/rc6.h
./Cellar/cryptopp/5.6.1/include/cryptopp/resource.h
./Cellar/cryptopp/5.6.1/include/cryptopp/rijndael.h
./Cellar/cryptopp/5.6.1/include/cryptopp/ripemd.h
./Cellar/cryptopp/5.6.1/include/cryptopp/rng.h
./Cellar/cryptopp/5.6.1/include/cryptopp/rsa.h
./Cellar/cryptopp/5.6.1/include/cryptopp/rw.h
./Cellar/cryptopp/5.6.1/include/cryptopp/safer.h
./Cellar/cryptopp/5.6.1/include/cryptopp/salsa.h
./Cellar/cryptopp/5.6.1/include/cryptopp/seal.h
./Cellar/cryptopp/5.6.1/include/cryptopp/secblock.h
./Cellar/cryptopp/5.6.1/include/cryptopp/seckey.h
./Cellar/cryptopp/5.6.1/include/cryptopp/seed.h
./Cellar/cryptopp/5.6.1/include/cryptopp/serpent.h
./Cellar/cryptopp/5.6.1/include/cryptopp/serpentp.h
./Cellar/cryptopp/5.6.1/include/cryptopp/sha.h
./Cellar/cryptopp/5.6.1/include/cryptopp/shacal2.h
./Cellar/cryptopp/5.6.1/include/cryptopp/shark.h
./Cellar/cryptopp/5.6.1/include/cryptopp/simple.h
./Cellar/cryptopp/5.6.1/include/cryptopp/skipjack.h
./Cellar/cryptopp/5.6.1/include/cryptopp/smartptr.h
./Cellar/cryptopp/5.6.1/include/cryptopp/socketft.h
./Cellar/cryptopp/5.6.1/include/cryptopp/sosemanuk.h
./Cellar/cryptopp/5.6.1/include/cryptopp/square.h
./Cellar/cryptopp/5.6.1/include/cryptopp/stdcpp.h
./Cellar/cryptopp/5.6.1/include/cryptopp/strciphr.h
./Cellar/cryptopp/5.6.1/include/cryptopp/tea.h
./Cellar/cryptopp/5.6.1/include/cryptopp/tiger.h
./Cellar/cryptopp/5.6.1/include/cryptopp/trdlocal.h
./Cellar/cryptopp/5.6.1/include/cryptopp/trunhash.h
./Cellar/cryptopp/5.6.1/include/cryptopp/ttmac.h
./Cellar/cryptopp/5.6.1/include/cryptopp/twofish.h
./Cellar/cryptopp/5.6.1/include/cryptopp/validate.h
./Cellar/cryptopp/5.6.1/include/cryptopp/vmac.h
./Cellar/cryptopp/5.6.1/include/cryptopp/wait.h
./Cellar/cryptopp/5.6.1/include/cryptopp/wake.h
./Cellar/cryptopp/5.6.1/include/cryptopp/whrlpool.h
./Cellar/cryptopp/5.6.1/include/cryptopp/winpipes.h
./Cellar/cryptopp/5.6.1/include/cryptopp/words.h
./Cellar/cryptopp/5.6.1/include/cryptopp/xtr.h
./Cellar/cryptopp/5.6.1/include/cryptopp/xtrcrypt.h
./Cellar/cryptopp/5.6.1/include/cryptopp/zdeflate.h
./Cellar/cryptopp/5.6.1/include/cryptopp/zinflate.h
./Cellar/cryptopp/5.6.1/include/cryptopp/zlib.h
./Cellar/cryptopp/5.6.1/INSTALL_RECEIPT.json
./Cellar/cryptopp/5.6.1/lib
./Cellar/cryptopp/5.6.1/lib/libcryptopp.a
./Cellar/cryptopp/5.6.1/LICENSE
./Cellar/cryptopp/5.6.1/README
./Cellar/openssl/0.9.8r/include/openssl/crypto.h
./Cellar/openssl/0.9.8r/lib/libcrypto.0.9.8.dylib
./Cellar/openssl/0.9.8r/lib/libcrypto.a
./Cellar/openssl/0.9.8r/lib/libcrypto.dylib
./Cellar/openssl/0.9.8r/lib/pkgconfig/libcrypto.pc
./Cellar/openssl/0.9.8r/share/man/man3/crypto.3
./Cellar/openssl/0.9.8r/share/man/man3/ERR_load_crypto_strings.3
./Cellar/openssl/0.9.8s/include/openssl/crypto.h
./Cellar/openssl/0.9.8s/lib/libcrypto.0.9.8.dylib
./Cellar/openssl/0.9.8s/lib/libcrypto.a
./Cellar/openssl/0.9.8s/lib/libcrypto.dylib
./Cellar/openssl/0.9.8s/lib/pkgconfig/libcrypto.pc
./Cellar/openssl/0.9.8s/share/man/man3/crypto.3ssl
./Cellar/openssl/0.9.8s/share/man/man3/ERR_load_crypto_strings.3ssl
./Cellar/pyqt/4.9.1/share/sip/QtCore/qcryptographichash.sip
./Cellar/qt/4.8.0/lib/QtCore.framework/Versions/4/Headers/qcryptographichash.h
./include/cryptopp
./lib/libcryptopp.a
./Library/Aliases/libcryptopp
./Library/Formula/cryptopp.rb
./Library/LinkedKegs/cryptopp
Should I try linking to the ones installed with openssl? pkgconfig and libcrypto.dylib are there. |
|
|
|
|
You should look at armory. The offline transactions keep your private keys from ever being on a system that is connected to the internet. It means you need 2 computers, but it is the most secure way to keep your coins.
|
|
|
|
TorusJKL just submitted a pull request, for a small change to the wallet-migration code that will allow it work on OSX. I'll update and push that change, now. In his pull request, I see that he created a paste: Building Bitcoin Armory on Mac OS X 10.6.x using Homebrew. It looks more complete than the instructions I have had posted, so it might be worth trying ( Splatster!). Please, someone look at that and tell me if it works! No luck on Lion  I can't get bsddb3 or cppForSwig to build $ make swig
g++ -c -O2 -pipe -I/usr/include/cryptopp -Icryptopp -fPIC -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS EncryptionUtils.cpp
swig -c++ -python -classic -outdir ../ -v CppBlockUtils.i
Language subdirectory: python
Search paths:
./
./swig_lib/python/
/Users/bwstitt/.homebrew/Cellar/swig/2.0.4/share/swig/2.0.4/python/
./swig_lib/
/Users/bwstitt/.homebrew/Cellar/swig/2.0.4/share/swig/2.0.4/
Preprocessing...
Starting language-specific parse...
EncryptionUtils.h:178: Warning 362: operator= ignored
Processing types...
EncryptionUtils.h:133: Warning 402: Base class 'BinaryData' is incomplete.
BtcUtils.h:58: Warning 402: Only forward declaration 'BinaryData' was found.
C++ analysis...
Generating wrappers...
BlockObj.h:76: Warning 509: Overloaded method BlockHeader::BlockHeader(BinaryData const *) effectively ignored,
BlockObj.h:73: Warning 509: as it is shadowed by BlockHeader::BlockHeader(BinaryData const &).
BlockUtils.h:265: Warning 472: Overloaded method BtcAddress::BtcAddress(BinaryData) with no explicit typecheck typemap for arg 0 of type 'BinaryData'
BlockUtils.h:265: Warning 472: Overloaded method BtcAddress::BtcAddress(BinaryData) with no explicit typecheck typemap for arg 0 of type 'BinaryData'
BlockUtils.h:265: Warning 472: Overloaded method BtcAddress::BtcAddress(BinaryData) with no explicit typecheck typemap for arg 0 of type 'BinaryData'
BlockUtils.h:265: Warning 472: Overloaded method BtcAddress::BtcAddress(BinaryData) with no explicit typecheck typemap for arg 0 of type 'BinaryData'
BlockUtils.h:265: Warning 472: Overloaded method BtcAddress::BtcAddress(BinaryData) with no explicit typecheck typemap for arg 0 of type 'BinaryData'
BlockUtils.h:306: Warning 509: Overloaded method BtcAddress::addTxIO(TxIOPair &) effectively ignored,
BlockUtils.h:305: Warning 509: as it is shadowed by BtcAddress::addTxIO(TxIOPair *).
BlockUtils.h:305: Warning 509: Overloaded method BtcAddress::addTxIO(TxIOPair *,bool) effectively ignored,
BlockUtils.h:306: Warning 509: as it is shadowed by BtcAddress::addTxIO(TxIOPair &,bool).
BlockUtils.h:346: Warning 472: Overloaded method BtcWallet::addAddress(BinaryData) with no explicit typecheck typemap for arg 1 of type 'BinaryData'
BlockUtils.h:346: Warning 472: Overloaded method BtcWallet::addAddress(BinaryData) with no explicit typecheck typemap for arg 1 of type 'BinaryData'
BlockUtils.h:346: Warning 472: Overloaded method BtcWallet::addAddress(BinaryData) with no explicit typecheck typemap for arg 1 of type 'BinaryData'
BlockUtils.h:346: Warning 472: Overloaded method BtcWallet::addAddress(BinaryData) with no explicit typecheck typemap for arg 1 of type 'BinaryData'
BlockUtils.h:346: Warning 472: Overloaded method BtcWallet::addAddress(BinaryData) with no explicit typecheck typemap for arg 1 of type 'BinaryData'
BlockUtils.h:627: Warning 472: Overloaded method BlockDataManager_FullRAM::addNewBlockData(BinaryData) with no explicit typecheck typemap for arg 1 of type 'BinaryData'
BlockUtils.h:627: Warning 472: Overloaded method BlockDataManager_FullRAM::addNewBlockData(BinaryData) with no explicit typecheck typemap for arg 1 of type 'BinaryData'
BtcUtils.h:915: Warning 472: Overloaded method BtcUtils::verifyProofOfWork(BinaryDataRef,BinaryDataRef) with no explicit typecheck typemap for arg 0 of type 'BinaryData'
g++ -I/usr/include/python2.7 -c -O2 -pipe -I/usr/include/cryptopp -Icryptopp -fPIC -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -lcryptopp -lpthread -lpython2.7 CppBlockUtils_wrap.cxx
i686-apple-darwin11-llvm-g++-4.2: -lcryptopp: linker input file unused because linking not done
i686-apple-darwin11-llvm-g++-4.2: -lpthread: linker input file unused because linking not done
i686-apple-darwin11-llvm-g++-4.2: -lpython2.7: linker input file unused because linking not done
In file included from /usr/include/python2.7/Python.h:127,
from CppBlockUtils_wrap.cxx:151:
/usr/include/python2.7/modsupport.h:27: warning: ‘PyArg_ParseTuple’ is an unrecognized format function type
i686-apple-darwin11-llvm-g++-4.2: -lcryptopp: linker input file unused because linking not done
i686-apple-darwin11-llvm-g++-4.2: -lpthread: linker input file unused because linking not done
i686-apple-darwin11-llvm-g++-4.2: -lpython2.7: linker input file unused because linking not done
#g++ -c -O2 -pipe -I/usr/include/cryptopp -Icryptopp -fPIC -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -lcryptopp -lpthread -lpython2.7 ECDSA_cryptopp.cpp
#g++ -o ECDSA_test.out -I/usr/include/cryptopp -Icryptopp -fPIC -DUSE_CRYPTOPP -D__STDC_LIMIT_MACROS -lcryptopp -lpthread -lpython2.7 ECDSA_cryptopp.cpp
g++ -shared -lcryptopp -lpthread -lpython2.7 UniversalTimer.o BinaryData.o BtcUtils.o BlockObj.o BlockObjRef.o BlockUtils.o EncryptionUtils.o CppBlockUtils_wrap.o -o ../_CppBlockUtils.so
ld: library not found for -lcryptopp
collect2: ld returned 1 exit status
make: *** [swig] Error 1
Also, bitcoinarmory.com's download page still points to .56-alpha, not .60-alpha |
|
|
|
You probably are located un USA? I did not see the availability of Collectors Edition un EU.
Yeah. I'm in the US. |
|
|
|
Yes, but you've been running for awhile. When you ran your p2pool node for the very first time how long did it take?
I'm pretty sure I had 10 in under a minute when I first setup, too. My backup node is much newer and it got connections just as fast as the server that has been up since January. I have a public IP, so theres no UPNP on my primary. I thought that might make a difference at first, but my secondary node has the port firewalled and no UPNP either. It should have a harder time getting connections, but it still gets them just as fast. Maybe try adding " -n p2pool.stitthappens.com:8335" to your command? That should get you connected to me at the very least. Theres a list of public nodes on http://nodes.p2pmine.com/, but that lists the worker port instead of the p2p port. |
|
|
|
Your node has to be running for a while without the IP changing. It took me 12 hours (over night) before I saw my first connection. It was a few weeks later when I saw higher numbers.
I see my first few connections pretty much instantly. And I get to 10 really fast. I just restarted my miner to update and am back at 13 peers in under a minute. |
|
|
|
I've got the collectors edition preordered. I'm excited. Mass effect 3 didn't last long enough |
|
|
|
|
You don't have to worry about 32 vs 64 bit with Mac. All of them have been 64 bit for a while now.
And while a mac mini may be more pricey than some other PCs. Try to find a computer that size with an internal power supply, a core i5, thunderbolt, wireless N, the best customer support, etc. It's not as expensive as it looks when you look at what you are actually buying.
I may be able to setup a legal VM for you. Actually, I may be able to borrow a previous-gen mac mini from a friend. I'll PM you when I know more.
|
|
|
|
I wish I could find the email, but Thunderbird search is failing me... Someone emailed me a month ago to tell me that the directions on the Building Armory from Source page worked flawlessly on his OSX installation except for one line: /usr/local/share/python/easy_install-2.7 twisted (just needed to add the abs path to the easy_install) I updated it in the build instructions, but never followed up with anyone else about it. I guess that's not the case for everyone (anyone?). I would track down the email but I remember that's all he said. And I still don't have any Mac/OSX system on which to try it (and even if I did, I'm not sure I would know how). I guess I'm going to need to get a Mac system, do it myself, and then compile binaries... but Macs are expensive... I think that person was using snow leopard. I used the linked directions on my Lion system and had no luck. With lots of fuxing around, I got it to this: $ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
Armory Version: 0.55
PyBtcAddress Version: 1.00
PyBtcWallet Version: 1.35
Detected Operating system: Mac/OSX
User home-directory : /Users/bwstitt/Library/Application Support
Satoshi BTC directory : /Users/bwstitt/Library/Application Support/Bitcoin/
Satoshi blk0001.dat : /Users/bwstitt/Library/Application Support/Bitcoin/blk0001.dat
Armory home dir : /Users/bwstitt/Library/Application Support/Armory/
Fatal Python error: Interpreter not initialized (version mismatch?)
Abort trap: 6
Perhaps it's worth starting a separate Armory+OSX thread in the Alt Clients subforum. Mainly because I have absolutely no experience with OSX at all. I've never even touched an OSX machine. And at the moment, I couldn't dig into it even if I wanted to (no access to such a machine). On the other hand, if others dig in and have a place to discuss it, I will happily offer as much assistance as I can, and then I'll have some place to go when I finally do get my hands on such a machine, and maybe it'll soften the blow for me to get into it... On that note, if I were to start searching craigslist or ebay for a Mac, what should I get? Presumably, something "relevant" but not anywhere near top-of-the-line, either. I would probably start on it, myself, when I am finished with RAM-reduction, so I especially don't need anything too powerful. Well this is kinda OT, but if you buy a mac, I HIGHLY recommend you buy it from apple. Apple has the best customer service for computers by far and if you buy from craigslist or some 3rd party, you don't get that. Mac minis start at $599. All you'll need after that is a monitor that supports HDMI or DVI. |
|
|
|
Meh... way too much variance to even pin it down to a day at this point.
I thought we were only like 2 days off from expected if you count from the genesis block. |
|
|
|
I wish I could find the email, but Thunderbird search is failing me... Someone emailed me a month ago to tell me that the directions on the Building Armory from Source page worked flawlessly on his OSX installation except for one line: /usr/local/share/python/easy_install-2.7 twisted (just needed to add the abs path to the easy_install) I updated it in the build instructions, but never followed up with anyone else about it. I guess that's not the case for everyone (anyone?). I would track down the email but I remember that's all he said. And I still don't have any Mac/OSX system on which to try it (and even if I did, I'm not sure I would know how). I guess I'm going to need to get a Mac system, do it myself, and then compile binaries... but Macs are expensive... I think that person was using snow leopard. I used the linked directions on my Lion system and had no luck. With lots of fuxing around, I got it to this: $ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
Armory Version: 0.55
PyBtcAddress Version: 1.00
PyBtcWallet Version: 1.35
Detected Operating system: Mac/OSX
User home-directory : /Users/bwstitt/Library/Application Support
Satoshi BTC directory : /Users/bwstitt/Library/Application Support/Bitcoin/
Satoshi blk0001.dat : /Users/bwstitt/Library/Application Support/Bitcoin/blk0001.dat
Armory home dir : /Users/bwstitt/Library/Application Support/Armory/
Fatal Python error: Interpreter not initialized (version mismatch?)
Abort trap: 6
|
|
|
|
|
Show Posts
