Topic: [Official] ROKOS [flavors] Crypto Full node OS |IoT Devices |Feedback/Discussion - page 18. (Read 74783 times)

ROKOS Flavors integrated coming coins wallets previews:

Blackcoin BLK/BC https://bitcointalk.org/index.php?topic=469640.new#new

There is a problem on dogecoin code to run over the new debian jessie based systems, Doge should fix this problem before we can integrate it into Pi 2 debian systems, I will gladly help if I get some free time and get contacted by them after this coming ROKOS flavors release.

Doge issue over Jessie: https://www.raspberrypi.org/forums/viewtopic.php?t=131452&p=876876 (reddit & Github links)

your welcome


I typed both the export lines

i then did the ./autogen.sh and at  the end it says:

Makefile.am:5: warning: user variable 'GZIP_ENV' defined here ...
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake variable 'GZIP_ENV' defined here

Makefile.am:55: warning: user target 'distcleancheck' defined here ...
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake target 'distcleancheck' defined here
src/Makefile.am:426 warning: user target '.mm.o' defined here ... /usr/share/automake-1.14/am/depend2.am: ... overrides Automake target 'mm.o' defined here

then i do the ./configure --enable-upnp-default --with-gui and thats when i get the missing cxx headers message

ROKOS Flavors integrated coming coins wallets previews:

Gamecredits GMC https://bitcointalk.org/index.php?topic=1266597.new#new

ROKOS Flavors integrated coming coins wallets previews:

Transfer TX https://bitcointalk.org/index.php?topic=1203975.new#new

ROKOS Flavors integrated coming coins wallets previews:

Diamond DMD https://bitcointalk.org/index.php?topic=580725.new#new

ROKOS Flavors integrated coming coins wallets previews:

Metalcoin METAL https://bitcointalk.org/index.php?topic=1101724.new#new





*submitted commit to add missing folders for compilation to github

ROKOS Flavors integrated coming coins wallets previews:

Europecoin ERC https://bitcointalk.org/index.php?topic=901605.new#new

Remember to do this commands before you start a new wallet compilation.


That will do

Thanks for your support and kind words.

following my success in installing the bitcoin 0.12.0 update i thought i'd give installing other wallets another go.
while going through the process of installing doge coin i type:
./configure --enable-upnp-default --with-gui
and it gets to checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing
do i need to install anything extra or type any extra commands in order to progress?

thanks
sani

ps
sorry for your loss oktoshi

- Bootstrap (Normal and Instant Chain) updated to February 11 2016.
http://bit.ly/OKchain

- OKCash is now an official sponsor for Cordica 21 (Integral school with national and International soccer tournaments for Kids with Down Syndrome [Mexico])
http://cordica21.org


ROKOS added as featured Partner for CoinFestUK
http://coinfestuk.org/#partnerships

- ROKOS flavors (small delay, lost a familiar to cancer this past days and been a bit busy in the process, will get released in less than 15 days)

- ROKOS core:  more than 1200 downloads! Thanks for your Support

not trying to be pushy but hoping to get an idea of rough ETA for your flavors release? Very much looking forward to it!

Ok, thanks
Yes, I can see my coins staking again.
I wait for the update.

Anders

Please have a read at the Readme.txt file on ROKOS desktop, your coins are always safe.

**************** Readme.txt ******************

Welcome to ROKOS v4 Included Cryptocurrencies Overview Report.

BTC Bitcoin: Graphical Client working 100%

BTC Bitcoin: Node working 100%

**

OK OKCash: Node working 100%

OK OKCash: Graphical Client Functional (stakes, sends recieve etc) 100% with Graphical bug (Thanks to QT over Pi v)

Details: The graphical client does all the functions correctly,
the Graphical bug happens thanks to The latest QT version
(a glitch it has over Raspberry Pi devices).

You can use the debug console to check for any balance or wallet info,
or It can be fixed to some degree by doing the next steps:

1. Open the wallet.

2. Right click and click on "Inspect".

3. Click on the red cross icon at the bottom right side of the new window.

4. write:   connectSignals(event)         
and click Enter and close this Inspection window.

5. You can now see the transactions and new address in the wallet.

Extra info: 

You can use console commands to get all the acurate info.

sample: open console and type:  getbalance

All the coins are safe and staking properly, the only visual glitch happens in
the graphical client on the view mode of transactions/coins thanks to Qt.
     
Will get fixed in upcoming releases with the evolution of Raspberry Pi and Qt software.

Location of nodes: /usr/local/bin/

Enjoy.
Best Regards.

~ OKtoshi

*********************************************

Do you have a miner? As a raspberrypi doesn't have the computing power to mine by its self

downloading again and going to set it up as normal when its all setup any tips on hoiw to solo mine for bitcoins using the core client cheers

have a screenshot?

This is not working out for me. Had some okcoins on Bittrex, send them to my Rokos okcoin wallet, but there is no coins. Got a notification window telling me  that there are incoming coins and I could se them for a while, under "staking" indicator in the right bottom corner, but now they are not even there.

Can someone help me with this?

By using -J2 we are indicating the compiler to use 2 cores from the processor, this speeds up the process a lot, but if you have more programs open and you are using resources while building then it will throw up a memory exhaust problem, to avoid one can do 1 of the 2 solutions,

1st) just use   make     instead of  make -J2

2nd option) close every open program except for the terminal to do the compilation with the -J2 flag.

Oh, well... the plague of low memory seems to strike again: https://bitcointalksearch.org/topic/solved-g-internal-compiler-error-killed-program-cc1plus-304389
Try increasing your swap space and/or freeing some memory.
Did you try to compile it from CLI environment (not starting X)?