@Wellenreiter

My recommendations:

1.) And MOST IMPORTANT, put some documentation to the source code part of the wallet page (https://www.feathercoin.com/#dls). In the moment one ends directly in the git repository. And I tried to build the current snapshot. E.g. what is a version guaranteed to work? Something like

git clone https://github.com/FeatherCoin/Feathercoin.git
cd Feathercoin
git checkout <hash>

would be nice.

2.) Put sufficient information to doc/build-unix (and clearly also to the other OS’), e.g., “use-qrencode=no” is not part of the documentation. Also the connection between qrencode and zebracrossing is not obvious!

3.) DO NOT HIDE this essential information in a forum. Might be possible that everything can be found here. However, people do not want to work through hundreds of posts until they find some potential solution to there problem.

Thanks

Hi tmuir12,

thanks for the info. I was aware of this thread but not able to post. It seems to work now. I ask, because p2pool.neoscrypt.de was mentioned by Calem in the neoscrypt testing thread.

Hi,

why can’t you also provide the corresponding signatures at the download page:

https://www.feathercoin.com/

???

Clearly, an experienced user will dig deeper and will look into the github-respository (which can also be found at the page above):

https://github.com/FeatherCoin/Feathercoin

There, one has to find the link to the release history (below “What is Feathercoin?”):

https://github.com/FeatherCoin/Feathercoin/releases

Here, signatures can be found (asc-files). However, still the public key-ID is missing, with which the binaries can be verified. Obviously, a

gpg --verify feathercoin-0.13.0-linux32.tar.gz.asc feathercoin-0.13.0-linux32.tar.gz

Tells one, which key must be imported: 4751434E. So asking

https://keyserver.ubuntu.com

for “peter bushnell” returns

https://keyserver.ubuntu.com/pks/lookup?op=vindex&search=peter+bushnell&fingerprint=on

At least this seems fine even though the key was registered 2018-02-19 and thus is quite new. Anyone could have provided the binaries and anyone could have registered the key under the name “peter bushnell”.

Is it so hard to put also the signatures as well as the key-ID on the download page?

Regards,
cu

@curiosity81 Manual still works for the current version 0.9.6.0 of feathercoin-qt and there is no error message anymore.

This manual is for a i386-Debian 8-system (Jessie).

Start via:

sudo apt-get update

Install some necessary packages, I am not sure what is really needed since this is stuff is needed for building namecoin-qt but maybe some of the feathercoin developers can enlighten me:

sudo apt-get install libboost-chrono-dev libboost-date-time-dev libboost-filesystem-dev libboost-program-options-dev libboost-serialization-dev libboost-system-dev libboost-thread-dev libboost-dev libminiupnpc-dev git qt4-qmake libqt4-dev build-essential qt4-linguist-tools libssl-dev

Install additional packages needed for feathercoin:

sudo apt-get install libboost1.55-all-dev autogen dh-autoreconf pkg-config libqrencode-dev libprotobuf-dev protobuf-compiler qtbase5-dev libqt5core5a libqt5gui5 libqt5dbus5 qttools5-dev qttools5-dev-tools

Now, suppose, that we are in

/home/user/stuff

We need Berkeley-DB 4.8 (do we???), get it:

wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz
echo "12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef db-4.8.30.NC.tar.gz" | sha256sum -c
tar -xzvf db-4.8.30.NC.tar.gz

Make directory for installing db-4.8 since we don’t want to install it in the system:

mkdir /home/user/stuff/db-4.8

Now, build db-4.8:

cd db-4.8.30.NC/build_unix/
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=/home/user/stuff/db-4.8
make
make install

Get this stupid zxing-library which seems not to exist (sorry, but no other coin needs this):

wget http://download.opensuse.org/repositories/home:/wellenreiter01/Debian_7.0/i386/libzxing_1.0-1.0_i386.deb
dpkg -i libzxing_1.0-1.0_i386.deb

(It only contains headers, alternatively one could install them via

ar -x libzxing_1.0-1.0_i386.deb
tar -xzvf data.tar.gz

and then copying the headers to the corresponding place by hand.)

Finally, we build feathercoin:

git clone https://github.com/FeatherCoin/Feathercoin.git
cd Feathercoin
./autogen.sh
./configure LDFLAGS="-L/home/user/stuff/db-4.8/lib/" CPPFLAGS="-I/home/user/stuff/db-4.8/include/" --with-boost-libdir=/usr/lib/i386-linux-gnu --with-gui=qt5
make

Building ends with an error message, but the feathercoin-qt binary should be located in src/qt.

Good night.

Thanks uncle_muddy, this is good to know!

Are the pools mentioned at https://forum.feathercoin.com/index.php?/topic/7780-neoscrypt-gpu-miner-public-beta-test/ also ready for FTC-mining? p2pool.neoscrypt.de was down the day before yesterday. Maybe it was adapted to FTC. Does anyone know more?

Hi AcidD,

Are you asking for the PGP keys to be linked on the main site ?

exactly! This is is what I am complaining about. It would be much better to list or link the gpg public keys prominently at www.feathercoin.com. As well as the forum ID of the person to whom the keys belong.

It’s like: “Hey guys, even if I cannot fully proof, that the correct person has built the binaries but here is the link to the gpg public keys. If I am a hacker then I must have hacked the feathercoin main page, the github repository as well as the corresponding forum account. This is very very unlikely.”

Last but not least, each coin project “hides” the signatures and keys differently. And it is often some work to get the needed information. If google is necessary to find this information, then it is too hard for the average person to verify the binaries.

And if someone uses an unverified and altered binary and loses real money, then this is bad publicity for feathercoin. (Showing that “There is no such thing as bad publicity” is not always true!)

Best regards,
cu

Hi,

why can’t you also provide the corresponding signatures at the download page:

https://www.feathercoin.com/

???

Clearly, an experienced user will dig deeper and will look into the github-respository (which can also be found at the page above):

https://github.com/FeatherCoin/Feathercoin

There, one has to find the link to the release history (below “What is Feathercoin?”):

https://github.com/FeatherCoin/Feathercoin/releases

Here, signatures can be found (asc-files). However, still the public key-ID is missing, with which the binaries can be verified. Obviously, a

gpg --verify feathercoin-0.13.0-linux32.tar.gz.asc feathercoin-0.13.0-linux32.tar.gz

Tells one, which key must be imported: 4751434E. So asking

https://keyserver.ubuntu.com

for “peter bushnell” returns

https://keyserver.ubuntu.com/pks/lookup?op=vindex&search=peter+bushnell&fingerprint=on

At least this seems fine even though the key was registered 2018-02-19 and thus is quite new. Anyone could have provided the binaries and anyone could have registered the key under the name “peter bushnell”.

Is it so hard to put also the signatures as well as the key-ID on the download page?

Regards,
cu

@curiosity81 Manual still works for the current version 0.9.6.0 of feathercoin-qt and there is no error message anymore.

@wrapper Nope, Namecoin works differently: clone it from git, enter the directory, do qmake and then make. Done. Provided the dependencies are available.

No! Did not work. Building ends with

snapwidget.cpp:10:51: fatal error: zxing/common/GlobalHistogramBinarizer.h: No such file or directory
#include "zxing/common/GlobalHistogramBinarizer.h"

So in the moment one has to compile it with xzing …

Ahhh … somewhere else you wrote, that building with no libzxing is done via

--with-qrcode=no

this seems to work. So the configuration call would look as follows:

./configure LDFLAGS="-L/home/user/stuff/db-4.8/lib/" CPPFLAGS="-I/home/user/stuff/db-4.8/include/" --with-boost-libdir=/usr/lib/i386-linux-gnu --with-gui=qt5 --with-qrcode=no

There is no configure parameter

use-qrencode=no

It is not accepting this, or

-use-qrencode=no
--use-qrencode=no

It accepts

--with-qrencode=no

but configure ends with a warning that this parameter is unknown. I also tried combinations with libzxing and similar with no effect.

@Wellenreiter

My recommendations:

1.) And MOST IMPORTANT, put some documentation to the source code part of the wallet page (https://www.feathercoin.com/#dls). In the moment one ends directly in the git repository. And I tried to build the current snapshot. E.g. what is a version guaranteed to work? Something like

git clone https://github.com/FeatherCoin/Feathercoin.git
cd Feathercoin
git checkout <hash>

would be nice.

2.) Put sufficient information to doc/build-unix (and clearly also to the other OS’), e.g., “use-qrencode=no” is not part of the documentation. Also the connection between qrencode and zebracrossing is not obvious!

3.) DO NOT HIDE this essential information in a forum. Might be possible that everything can be found here. However, people do not want to work through hundreds of posts until they find some potential solution to there problem.

Thanks

This manual is for a i386-Debian 8-system (Jessie).

Start via:

sudo apt-get update

Install some necessary packages, I am not sure what is really needed since this is stuff is needed for building namecoin-qt but maybe some of the feathercoin developers can enlighten me:

sudo apt-get install libboost-chrono-dev libboost-date-time-dev libboost-filesystem-dev libboost-program-options-dev libboost-serialization-dev libboost-system-dev libboost-thread-dev libboost-dev libminiupnpc-dev git qt4-qmake libqt4-dev build-essential qt4-linguist-tools libssl-dev

Install additional packages needed for feathercoin:

sudo apt-get install libboost1.55-all-dev autogen dh-autoreconf pkg-config libqrencode-dev libprotobuf-dev protobuf-compiler qtbase5-dev libqt5core5a libqt5gui5 libqt5dbus5 qttools5-dev qttools5-dev-tools

Now, suppose, that we are in

/home/user/stuff

We need Berkeley-DB 4.8 (do we???), get it:

wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz
echo "12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef db-4.8.30.NC.tar.gz" | sha256sum -c
tar -xzvf db-4.8.30.NC.tar.gz

Make directory for installing db-4.8 since we don’t want to install it in the system:

mkdir /home/user/stuff/db-4.8

Now, build db-4.8:

cd db-4.8.30.NC/build_unix/
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=/home/user/stuff/db-4.8
make
make install

Get this stupid zxing-library which seems not to exist (sorry, but no other coin needs this):

wget http://download.opensuse.org/repositories/home:/wellenreiter01/Debian_7.0/i386/libzxing_1.0-1.0_i386.deb
dpkg -i libzxing_1.0-1.0_i386.deb

(It only contains headers, alternatively one could install them via

ar -x libzxing_1.0-1.0_i386.deb
tar -xzvf data.tar.gz

and then copying the headers to the corresponding place by hand.)

Finally, we build feathercoin:

git clone https://github.com/FeatherCoin/Feathercoin.git
cd Feathercoin
./autogen.sh
./configure LDFLAGS="-L/home/user/stuff/db-4.8/lib/" CPPFLAGS="-I/home/user/stuff/db-4.8/include/" --with-boost-libdir=/usr/lib/i386-linux-gnu --with-gui=qt5
make

Building ends with an error message, but the feathercoin-qt binary should be located in src/qt.

Good night.

I am pissed: the documentation of building feathercoin is a real mess.

What is my problem?

I tried to build feathercoin-qt on Debian jessie. Yes, I could use binaries created by Wellenreiter. However, in doubtful situations, I prefer to build the binary by myself. So I cloned into the git repository and tried to make the binary.

First, I could not build the binary via Qt4, because make could not find some Qt5-includes. Why??? I specified Qt4 when starting the configuration script, but no effect.

So I tried to build it via Qt5, unfortunately, these STUPID zxing-headers are missing and THERE IS NO corresponding package for Debian 8 or even Ubuntu, also ZebraCrossing is not existend. Arghhhh, why do you put such dependencies, when they are not in the git-repository??? Are they even necessary for a base simple GUI???

The solution, but a dirty one, was, to use the deb-file from Wellenreiter which only consists of headers. After almost finishing building, make complained about some tests which failed. Luckily, the binary was produced and is working.

Again, the documentation for building feathercoin or feathercoin-qt is a mess. There is no hint where to find building information at the main page (https://www.feathercoin.com/#dls). And the stuff in the git-repository is not complete.

It is quite likely, that, as dumb as I am, I have overseen crucial information … ich hab so einen Hals, sooo einen Hals, arghhhh >:( !!!

So I puked out enough my anger, my next post in a few minutes will be a manual which works on Debian 8. You can delete, keep or move it and comment, what I did wrongly. Thanks.