Topic: wallets in general on linux (Read 1541 times)

I think you must firstly check out right Linux OS for you - there are ~ 8 main Linux OS. For example Linux Centos - quite good. And then start to find wallet, which you can install in that Linux OS. If you are not experienced with Linux, you can try to find help in Linux forums 

Thanks for the further explanation it has been a real help.

Great explanation, will be hard to get a better one.

If OP cant install it with this info. Then will be hard.

If on ubuntu


Debian

In the above steps we gain access to libdb4.8 which at this point is safest as libdb5.1 won't work with wallets built with 4.8

Now the process should be the same for both distro's.


Debian users may need to use libboost1.49-all-dev rather than libboost1.54-all-dev but the above commands should install all the required prerequisites for both the daemon and the QT.

In order to actually make the coin it depends on if its based on the bitcoin 0.9 codebase or the 0.8 base.

If 0.9


if 0.8


you can also use the j flag in order to speed up building of the project. Here we assume I have access to 4 cores and am building bitcoin for source


Here we assume I only have access to 2 cores and am using litecoin

Thank you so much for your reply gjhiggins, it is really much appreciated. I finally got VTC to work and your answer has given me quite a few clues on how to get this stuff working!

Thanks!

Try the unix-specific build notes in /doc, e.g. https://github.com/neoscoin/NEOS/blob/master/doc/build-unix.md


The dependencies are usually listed in the unix-build doc, they are conveniently listed as a one-liner in the article: How To Clone Scrypt Based Altcoins for Fun and Profit, i.e. they should be satisfiable with:


If you experience problems with using the above to satisfy the dependencies then you might be better advised to install Vagrant, set up an Ubuntu 14.04 VM and work off've that.




that's likely just a large, flashing, red, warning sign of a classic CBA * developer, try the unix-build doc: https://github.com/HYPERcrypto/Hyper/blob/master/doc/build-unix.txt

Cheers

Graham


* Can't Be Arsed

Hey,
Thanks for the replies.

I've been trying to install wallets such as vTorrent, Blackcoin, Hyper, Cannacoin-Qt and many others.

I've tried reading the READMEs but they don't seem to provide much information.

They always pop up extremely obscure libraries that are missing:
libboost_system.so.1.48.0
libboost_system.so.1.46.0
libdb_cxx-5.1.so
(Cannacoin-Qt PoSV (Linux) won't run because libboost_system.so.1.46.1 is missing)

I've tried googling most of these to a ridiculous level and haven't really found any straightforward solutions. I've installed countless programs/libraries as suggested by the linux community but I still can't get most of my wallets to actually run.


Using vTorrent as an example,
I tried to do the following:
./make vTorrent-client.pro

first I get errors about qmake being missing and then brew being missing; so I spend half an hour googling how to install these two things (and then adding brew to my .bashrc which doesn't even work). End result is I still can't get it to compile, and the precompiled version doesn't work.

I get that I'm not an expert on linux--but why do these wallets (in their simplest terms: a piece of software that connects to other computers and sends/recieves data) need so many libraries? It absolutely beggars belief that cryptocurrency is this difficult to install on linux. I figured that by installing Ubuntu, and choosing pre-compiled pieces of software for Ubuntu the wallets would "just work". Far from it.

Why are there no standards on this? Every single one needs different libraries.

The worst part is that I'm fairly fluent at computers and willing to learn; if cryptocurrency is meant to be accessible to the masses it should be a lot easier than this to use (and yeah, I know its mostly community-driven, open source and whatnot, but its still a pain in the ass to use.


BTW, this is what the README.md looks like for HYPER's wallet:

Check the source code for Readme.txt which will point to the install info perhaps in the docs folder, build-unix or readme-qt.  these will mention dependancies such as:
for basic systems or more specific instructions for various flavors. Once you have the dependencies is where I walways have the issue as I'm a noob on linux and finding the right makefile or pro file is hard personally I end up typing run, install, blah, blah a bunch of itmes til it compiles (yes dont kill the noob)

its better to install most of the dependencies.
with Linux you can use: sudo add-apt-repository ppa: bitcoin/bitcoin
sudo apt-get update.

u can also quickly compile ur own wallets.

I have used Electrum on Linux and it was very easy to install following the instructions on the site.

It's used on a Pi usually so it's set up to be an all in one script. He said he had at least basic knowledge of Linux so I assumed he would read what a script does before running it. It's all VERY clearly labeled

lol yeah just ignore the part where it installs a firewall without telling you.

You should look at the script I posted for the BALLS wallet on Raspberry Pi. It will walk you through all the steps and works on both ARM and desktops

Use it to see how it works and read it to see what it does

Hi.

I use Centos Linux in my home PC and i have installed Bitcoin qt, and multibit on it. No problems for the installation.

What is the error you got when you try to install this wallets?

well right, sky is the limit for software in general

Coin wallets are all pretty much clones of each other so it helps to keep the variety of dependencies down.

I never compiled a wallet on Linux but I found with regular software it often breaks because of a particular version of a file that is missing. The file is usually easy to get but always results in an error saying it's the wrong version of the file.

actually I would guess at least 75% of all crypto wallets have the exact same dependencies

I think software breaking due to some obscure missing library file is a common event when using Linux. I often had the same problem when trying to compile non-crypto software. There are so many different Linux flavors that it must be extremely difficult to release software that works on all of them, and keep it updated so it keeps on working on all of them.

I think you can compile 32bit on 64bit but you need the libraries for that as 32bit. Google compiling 32bit on 64bit or similar..

post a wallet you are trying to install and I can walk you through it.

You should always compile from source.