Search content
Sort by
Showing 13 of 13 results by Wellenreiter
Re: Feathercoin [FTC] - time proven, fast, secure and unique POW coin
Hi Marada,
It seems all the dependencies are met now.
No! see below
There is no need to switch to bdb5.3, I've 0.9.3 running even on BDB 4.8 and 5.1
The only libprotobuf-dev can not be upgraded to >= 2.6.1 from 2.5.0-9 without messing up the whole LTS system, but I think it is not the case.
That should be no problem
As said I never used Linux mint, so I can't judge how the dependencies are resolved in that distribution.
Mint should use the same package structure as Ubuntu, so I checked the packages you need to have for Ubuntu.
With the help of Google I found the following:
QJsonObject: The compiler misses the file qjasonobject.h
As Mint is a kind of special flavor of Ubuntu I checked the Ubuntu packages.
You need to install the package qtbase5-dev. That package contains qjsonobject.h as you can see here:
http://packages.ubuntu.com/wily/amd64/qtbase5-dev/filelist
QtPrintSupport/QPrinter: The compiler misses the file qprinter.h
Again, the package qtbase5-dev contains the header files for QtPrintSupport.
If you have installed qtbase5-dev, check for the directories containing qprinter.h and qjsonobject.h
and specifiy these directories for the configure script. Use 'configure --help' for syntax.
I'm the only compiling option I'm aware of is that you have to run configure with the 'diable-tests' option.
use configure --help for syntax. Other possible 'special options' are platform dependencies and related to your local system so you need to find out yourself.
The only older version you could use is 0.8.7.1. other versions are not working as they are pre-neoscrypt.
[qoute]
I know many users are not aware of such details as they use binaries or even not.
Anyway I believe serious vendors evaluate the code quality to determine the team capability.
Therefore this situation doesn't help FTC getting shining again at all.
[/quote]
As you may notice from my answers above , the problems you have are NOT related to the code quality of the Feathercoin wallet, but are caused by some packets/dependencies missing on our development system.
Just a hint: check the file lists of the packages you have installed. In order to compile a programm you need the header files of the libraries, while to run the program you need the shared object files of the libraries. (*.h vs *.so)
Typicalliy the header files are contained in the -dev packages.
It seems all the dependencies are met now.
No! see below
Quote
I have even switched to bdb5.3 even though I would prefer to stick with 5.1.
There is no need to switch to bdb5.3, I've 0.9.3 running even on BDB 4.8 and 5.1
Quote
The only libprotobuf-dev can not be upgraded to >= 2.6.1 from 2.5.0-9 without messing up the whole LTS system, but I think it is not the case.
That should be no problem
Quote
Basically no progress, the result is still the same. It must have something to do with QtPrintSupport and QJsonObject.
As said I never used Linux mint, so I can't judge how the dependencies are resolved in that distribution.
Mint should use the same package structure as Ubuntu, so I checked the packages you need to have for Ubuntu.
With the help of Google I found the following:
QJsonObject: The compiler misses the file qjasonobject.h
As Mint is a kind of special flavor of Ubuntu I checked the Ubuntu packages.
You need to install the package qtbase5-dev. That package contains qjsonobject.h as you can see here:
http://packages.ubuntu.com/wily/amd64/qtbase5-dev/filelist
QtPrintSupport/QPrinter: The compiler misses the file qprinter.h
Again, the package qtbase5-dev contains the header files for QtPrintSupport.
If you have installed qtbase5-dev, check for the directories containing qprinter.h and qjsonobject.h
and specifiy these directories for the configure script. Use 'configure --help' for syntax.
Quote
What were "special compiling options" mentioned by entertheabyss?
Can I use older wallet versions that got build flawlessly?
Can I use older wallet versions that got build flawlessly?
I'm the only compiling option I'm aware of is that you have to run configure with the 'diable-tests' option.
use configure --help for syntax. Other possible 'special options' are platform dependencies and related to your local system so you need to find out yourself.
The only older version you could use is 0.8.7.1. other versions are not working as they are pre-neoscrypt.
[qoute]
I know many users are not aware of such details as they use binaries or even not.
Anyway I believe serious vendors evaluate the code quality to determine the team capability.
Therefore this situation doesn't help FTC getting shining again at all.
[/quote]
As you may notice from my answers above , the problems you have are NOT related to the code quality of the Feathercoin wallet, but are caused by some packets/dependencies missing on our development system.
Just a hint: check the file lists of the packages you have installed. In order to compile a programm you need the header files of the libraries, while to run the program you need the shared object files of the libraries. (*.h vs *.so)
Typicalliy the header files are contained in the -dev packages.
Re: Feathercoin [FTC] - time proven, fast, secure and unique POW coin
I can't compile the new Feathercoin wallet on linux (Linux Mint 17.3).
libqt5printsupport5 and libqjson-dev are installed.
Other wallets, including bitcoin-qt compile fine.
What is wrong?
PS: this was v. 0.9.3, github link from official FTC site.
Code:
coinnectordialog.cpp:28:23: fatal error: QJsonObject: No such file or directory
#include
^
compilation terminated.
(...)
make[5]: *** [libbitcoinqt_a-coinnectordialog.o] Error 1
utilitydialog.cpp:51:35: fatal error: QtPrintSupport/QPrinter: No such file or directory
#include
^
compilation terminated.
#include
^
compilation terminated.
(...)
make[5]: *** [libbitcoinqt_a-coinnectordialog.o] Error 1
utilitydialog.cpp:51:35: fatal error: QtPrintSupport/QPrinter: No such file or directory
#include
^
compilation terminated.
libqt5printsupport5 and libqjson-dev are installed.
Other wallets, including bitcoin-qt compile fine.
What is wrong?
PS: this was v. 0.9.3, github link from official FTC site.
I never tried to compile for Linux Mint, but I think you are missing some QT dependencies.
For Debian I compiled 0.9.3 and 0.9.5 with the follwing:
From the DSC file:
Code:
Build-Depends: libdb5.3-dev debhelper (>= 8.3.0), qtbase5-dev, qttools5-dev-tools, build-essential, libboost-dev,
libboost-system-dev, libboost-filesystem-dev, libboost-program-options-dev, libboost-thread-dev,
libssl-dev,libdb++-dev, libminiupnpc-dev, binutils,
autoconf, automake, debhelper (>= 8.1.3), dh-autoreconf,
libzxing, libqrencode-dev, pkg-config, libprotobuf-dev (>= 2.6.1), protobuf-compiler
libboost-system-dev, libboost-filesystem-dev, libboost-program-options-dev, libboost-thread-dev,
libssl-dev,libdb++-dev, libminiupnpc-dev, binutils,
autoconf, automake, debhelper (>= 8.1.3), dh-autoreconf,
libzxing, libqrencode-dev, pkg-config, libprotobuf-dev (>= 2.6.1), protobuf-compiler
Extract from the rules-file
Code:
#ifeq "$(shell uname -v|grep +deb7)" "+deb7"
GUI_PARMS= --with-gui=no
HAVE_GUI= false
#else
GUI_PARMS= --with-gui=qt5 --with-qrcode
HAVE_GUI= true
#endif
ifeq "$(shell uname -m)" "x86_64"
LIBDIR=$(PREFIX)/lib64
CONFIG_PARMS= --without-cli --with-incompatible-bdb --enable-tests=no $(GUI_PARMS) -with-boost=yes
else
LIBDIR=$(PREFIX)/lib
CONFIG_PARMS= --without-cli --with-incompatible-bdb --enable-tests=no $(GUI_PARMS) --with-boost-libdir=$(LIBDIR)/i386-linux-gnu
endif
#ifeq "$(shell uname -v| grep -c deb)" "1"
QRCODE="1"
#else
#QRCODE="-"
#endif
INCLUDEDIR=../../../include
SBINDIR=$(PREFIX)/sbin
MANDIR=$(PREFIX)/share/man
DATADIR=$(PREFIX)/share/$(NAME)
DOCDIR=$(PREFIX)/share/doc/$(NAME)
SYSCONFDIR=/etc
RCDIR=$(SYSCONFDIR)/init.d
CGIDIR=/src/www/cgi-bin
build: build-arch build-indep
build-arch: build-stamp
build-indep: build-stamp
build-stamp:
dh_testdir
dh_autoreconf
# Add here commands to compile the package.
./autogen.sh
./configure $(CONFIG_PARMS)
#
make
GUI_PARMS= --with-gui=no
HAVE_GUI= false
#else
GUI_PARMS= --with-gui=qt5 --with-qrcode
HAVE_GUI= true
#endif
ifeq "$(shell uname -m)" "x86_64"
LIBDIR=$(PREFIX)/lib64
CONFIG_PARMS= --without-cli --with-incompatible-bdb --enable-tests=no $(GUI_PARMS) -with-boost=yes
else
LIBDIR=$(PREFIX)/lib
CONFIG_PARMS= --without-cli --with-incompatible-bdb --enable-tests=no $(GUI_PARMS) --with-boost-libdir=$(LIBDIR)/i386-linux-gnu
endif
#ifeq "$(shell uname -v| grep -c deb)" "1"
QRCODE="1"
#else
#QRCODE="-"
#endif
INCLUDEDIR=../../../include
SBINDIR=$(PREFIX)/sbin
MANDIR=$(PREFIX)/share/man
DATADIR=$(PREFIX)/share/$(NAME)
DOCDIR=$(PREFIX)/share/doc/$(NAME)
SYSCONFDIR=/etc
RCDIR=$(SYSCONFDIR)/init.d
CGIDIR=/src/www/cgi-bin
build: build-arch build-indep
build-arch: build-stamp
build-indep: build-stamp
build-stamp:
dh_testdir
dh_autoreconf
# Add here commands to compile the package.
./autogen.sh
./configure $(CONFIG_PARMS)
#
make
For Debian 7 no Gui is possible, as Debian 7 uses QT4 and 0.9.3 / 0.9.5 doesn't compile on QT4
I hope this helps
The next relase which probably will be 0.11.2 compiles fine for QT4 and QT5
Re: Feathercoin [FTC] - time proven, fast, secure and unique POW coin
You need to scroll down until you reach the post from 'Wrapper'.
He compiled the code about 2 weeks ago and described the modifications to the original procedure and also describes his tests /attempts to get the miner working with different versions of the AMD drivers.
To my knowledge he compiled on Ubuntu, but may be able to help with other Linux OS, too.
He compiled the code about 2 weeks ago and described the modifications to the original procedure and also describes his tests /attempts to get the miner working with different versions of the AMD drivers.
To my knowledge he compiled on Ubuntu, but may be able to help with other Linux OS, too.
Re: Feathercoin [FTC] - time proven, fast, secure and unique POW coin
Yes, there are a lot of people mining Feathercoin with an AMD card.
I found this howto:
http://forum.feathercoin.com/topic/7446/guide-how-to-mine-ftc-neoscrypt-sgminer-ubuntu-14-04-amd/
I found this howto:
http://forum.feathercoin.com/topic/7446/guide-how-to-mine-ftc-neoscrypt-sgminer-ubuntu-14-04-amd/
Re: Feathercoin [FTC] - time proven, fast, secure and unique POW coin
i am having an issue building feathercoin:
Code:
base58_tests.cpp:93:10: note: bool base58_tests::TestAddrTypeVisitor::operator()(const CNoDestination&) const
bool operator()(const CNoDestination &no) const
^
base58_tests.cpp:93:10: note: no known conversion for argument 1 from CStealthAddress to const CNoDestination&
Makefile:881: recipe for target 'test_bitcoin-base58_tests.o' failed
make[4]: *** [test_bitcoin-base58_tests.o] Error 1
make[4]: *** Waiting for unfinished jobs....
Makefile:923: recipe for target 'test_bitcoin-bloom_tests.o' failed
make[4]: *** [test_bitcoin-bloom_tests.o] Error 1
make[4]: Leaving directory '/home/user/apps/Feathercoin/src/test'
Makefile:700: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/home/user/apps/Feathercoin/src/test'
Makefile:913: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/user/apps/Feathercoin/src'
Makefile:666: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/user/apps/Feathercoin/src'
Makefile:502: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
bool operator()(const CNoDestination &no) const
^
base58_tests.cpp:93:10: note: no known conversion for argument 1 from CStealthAddress to const CNoDestination&
Makefile:881: recipe for target 'test_bitcoin-base58_tests.o' failed
make[4]: *** [test_bitcoin-base58_tests.o] Error 1
make[4]: *** Waiting for unfinished jobs....
Makefile:923: recipe for target 'test_bitcoin-bloom_tests.o' failed
make[4]: *** [test_bitcoin-bloom_tests.o] Error 1
make[4]: Leaving directory '/home/user/apps/Feathercoin/src/test'
Makefile:700: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/home/user/apps/Feathercoin/src/test'
Makefile:913: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/user/apps/Feathercoin/src'
Makefile:666: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/user/apps/Feathercoin/src'
Makefile:502: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
The test section of the code is currently broken. It is not needed for a fully functional wallet.
you can disable the compilation of the tests by adding '--enable-tests=no' as parameter to the configure script.
FTC ist alive and has a busy community.
If you follow their forum, you will notice, that a lot of good things are on their way.
It seems people over there talk about their activities only, after a goal is archived, rather than making noise, before something is done.
If you follow their forum, you will notice, that a lot of good things are on their way.
It seems people over there talk about their activities only, after a goal is archived, rather than making noise, before something is done.
