doublec
Legendary
 Offline
Activity: 1078
Merit: 1005
|
 |
December 04, 2010, 06:41:31 AM |
|
|
|
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
jon_smark
Member
Offline
Activity: 90
Merit: 10
|
|
December 04, 2010, 09:41:19 PM |
|
Hi, I get a compilation error when building under Ubuntu Lucid in an x86_64 arch. I just got the latest version from github, and the only modification I made was adding the following code to the end of cmake-bitcoinr/CMakeLists.txt as described previously in this thread. IF(NOT WIN32)
TARGET_LINK_LIBRARIES(bitcoinr pthread)
ENDIF(NOT WIN32)
Anyway, though the invocation of 'cmake .' succeeds: -- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Boost version: 1.40.0
-- Found the following Boost libraries:
-- date_time
-- filesystem
-- program_options
-- regex
-- system
-- thread
-- Found OpenSSL: /usr/lib/libssl.so;/usr/lib/libcrypto.so
-- Found BerkeleyDB: /usr/lib/libdb.so
-- Configuring done
-- Generating done
-- Build files have been written to: /home/smark/software/bitcoin-pool
the actual compilation fails: smark@mymachine:~/software/bitcoin-pool$ make
[ 11%] Building CXX object cmake-bitcoinr/CMakeFiles/bitcoinr.dir/__/src/remote/remoteminerclient.cpp.o
In file included from /home/smark/software/bitcoin-pool/src/remote/../headers.h:127,
from /home/smark/software/bitcoin-pool/src/remote/remotebitcoinheaders.h:33,
from /home/smark/software/bitcoin-pool/src/remote/remoteminerclient.h:30,
from /home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp:19:
/home/smark/software/bitcoin-pool/src/remote/../net.h: In member function ‘void CNode::EndMessage()’:
/home/smark/software/bitcoin-pool/src/remote/../net.h:710: warning: invalid access to non-static data member ‘CMessageHeader::nMessageSize’ of NULL object
/home/smark/software/bitcoin-pool/src/remote/../net.h:710: warning: (perhaps the ‘offsetof’ macro was used incorrectly)
/home/smark/software/bitcoin-pool/src/remote/../net.h:718: warning: invalid access to non-static data member ‘CMessageHeader::nChecksum’ of NULL object
/home/smark/software/bitcoin-pool/src/remote/../net.h:718: warning: (perhaps the ‘offsetof’ macro was used incorrectly)
/home/smark/software/bitcoin-pool/src/remote/../net.h:719: warning: invalid access to non-static data member ‘CMessageHeader::nChecksum’ of NULL object
/home/smark/software/bitcoin-pool/src/remote/../net.h:719: warning: (perhaps the ‘offsetof’ macro was used incorrectly)
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp: In member function ‘void RemoteMinerClient::SendFoundHash(int64, const std::vector<unsigned char, std::allocator<unsigned char> >&, unsigned int)’:
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp:631: error: conversion from ‘long long int’ to ‘const json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >’ is ambiguous
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:283: note: candidates are: json_spirit::Value_impl<Config>::Value_impl(double) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:275: note: json_spirit::Value_impl<Config>::Value_impl(uint64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:267: note: json_spirit::Value_impl<Config>::Value_impl(int64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:259: note: json_spirit::Value_impl<Config>::Value_impl(int) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:251: note: json_spirit::Value_impl<Config>::Value_impl(bool) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:219: note: json_spirit::Value_impl<Config>::Value_impl(typename Config::String_type::const_pointer) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >] <near match>
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp:637: error: conversion from ‘int64’ to ‘const json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >’ is ambiguous
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:283: note: candidates are: json_spirit::Value_impl<Config>::Value_impl(double) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:275: note: json_spirit::Value_impl<Config>::Value_impl(uint64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:267: note: json_spirit::Value_impl<Config>::Value_impl(int64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:259: note: json_spirit::Value_impl<Config>::Value_impl(int) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:251: note: json_spirit::Value_impl<Config>::Value_impl(bool) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:219: note: json_spirit::Value_impl<Config>::Value_impl(typename Config::String_type::const_pointer) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >] <near match>
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp: In member function ‘void RemoteMinerClient::SendMetaHash(int64, const std::vector<unsigned char, std::allocator<unsigned char> >&, unsigned int, const std::vector<unsigned char, std::allocator<unsigned char> >&, const uint256&, unsigned int)’:
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp:658: error: conversion from ‘long long int’ to ‘const json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >’ is ambiguous
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:283: note: candidates are: json_spirit::Value_impl<Config>::Value_impl(double) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:275: note: json_spirit::Value_impl<Config>::Value_impl(uint64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:267: note: json_spirit::Value_impl<Config>::Value_impl(int64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:259: note: json_spirit::Value_impl<Config>::Value_impl(int) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:251: note: json_spirit::Value_impl<Config>::Value_impl(bool) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:219: note: json_spirit::Value_impl<Config>::Value_impl(typename Config::String_type::const_pointer) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >] <near match>
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp:664: error: conversion from ‘int64’ to ‘const json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >’ is ambiguous
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:283: note: candidates are: json_spirit::Value_impl<Config>::Value_impl(double) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:275: note: json_spirit::Value_impl<Config>::Value_impl(uint64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:267: note: json_spirit::Value_impl<Config>::Value_impl(int64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:259: note: json_spirit::Value_impl<Config>::Value_impl(int) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:251: note: json_spirit::Value_impl<Config>::Value_impl(bool) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:219: note: json_spirit::Value_impl<Config>::Value_impl(typename Config::String_type::const_pointer) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >] <near match>
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp:667: error: conversion from ‘int64’ to ‘const json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >’ is ambiguous
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:283: note: candidates are: json_spirit::Value_impl<Config>::Value_impl(double) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:275: note: json_spirit::Value_impl<Config>::Value_impl(uint64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:267: note: json_spirit::Value_impl<Config>::Value_impl(int64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:259: note: json_spirit::Value_impl<Config>::Value_impl(int) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:251: note: json_spirit::Value_impl<Config>::Value_impl(bool) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:219: note: json_spirit::Value_impl<Config>::Value_impl(typename Config::String_type::const_pointer) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >] <near match>
make[2]: *** [cmake-bitcoinr/CMakeFiles/bitcoinr.dir/__/src/remote/remoteminerclient.cpp.o] Error 1
make[1]: *** [cmake-bitcoinr/CMakeFiles/bitcoinr.dir/all] Error 2
make: *** [all] Error 2
Any idea of what might wrong here? Thanks in advance! Jon. |
|
|
|
|
matt
Newbie
Offline
Activity: 1
Merit: 0
|
|
December 04, 2010, 11:59:26 PM |
|
Hi, I get a compilation error when building under Ubuntu Lucid in an x86_64 arch. I just got the latest version from github, and the only modification I made was adding the following code to the end of cmake-bitcoinr/CMakeLists.txt as described previously in this thread. IF(NOT WIN32)
TARGET_LINK_LIBRARIES(bitcoinr pthread)
ENDIF(NOT WIN32)
Anyway, though the invocation of 'cmake .' succeeds: -- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Boost version: 1.40.0
-- Found the following Boost libraries:
-- date_time
-- filesystem
-- program_options
-- regex
-- system
-- thread
-- Found OpenSSL: /usr/lib/libssl.so;/usr/lib/libcrypto.so
-- Found BerkeleyDB: /usr/lib/libdb.so
-- Configuring done
-- Generating done
-- Build files have been written to: /home/smark/software/bitcoin-pool
the actual compilation fails: smark@mymachine:~/software/bitcoin-pool$ make
[ 11%] Building CXX object cmake-bitcoinr/CMakeFiles/bitcoinr.dir/__/src/remote/remoteminerclient.cpp.o
In file included from /home/smark/software/bitcoin-pool/src/remote/../headers.h:127,
from /home/smark/software/bitcoin-pool/src/remote/remotebitcoinheaders.h:33,
from /home/smark/software/bitcoin-pool/src/remote/remoteminerclient.h:30,
from /home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp:19:
/home/smark/software/bitcoin-pool/src/remote/../net.h: In member function ‘void CNode::EndMessage()’:
/home/smark/software/bitcoin-pool/src/remote/../net.h:710: warning: invalid access to non-static data member ‘CMessageHeader::nMessageSize’ of NULL object
/home/smark/software/bitcoin-pool/src/remote/../net.h:710: warning: (perhaps the ‘offsetof’ macro was used incorrectly)
/home/smark/software/bitcoin-pool/src/remote/../net.h:718: warning: invalid access to non-static data member ‘CMessageHeader::nChecksum’ of NULL object
/home/smark/software/bitcoin-pool/src/remote/../net.h:718: warning: (perhaps the ‘offsetof’ macro was used incorrectly)
/home/smark/software/bitcoin-pool/src/remote/../net.h:719: warning: invalid access to non-static data member ‘CMessageHeader::nChecksum’ of NULL object
/home/smark/software/bitcoin-pool/src/remote/../net.h:719: warning: (perhaps the ‘offsetof’ macro was used incorrectly)
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp: In member function ‘void RemoteMinerClient::SendFoundHash(int64, const std::vector<unsigned char, std::allocator<unsigned char> >&, unsigned int)’:
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp:631: error: conversion from ‘long long int’ to ‘const json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >’ is ambiguous
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:283: note: candidates are: json_spirit::Value_impl<Config>::Value_impl(double) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:275: note: json_spirit::Value_impl<Config>::Value_impl(uint64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:267: note: json_spirit::Value_impl<Config>::Value_impl(int64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:259: note: json_spirit::Value_impl<Config>::Value_impl(int) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:251: note: json_spirit::Value_impl<Config>::Value_impl(bool) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:219: note: json_spirit::Value_impl<Config>::Value_impl(typename Config::String_type::const_pointer) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >] <near match>
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp:637: error: conversion from ‘int64’ to ‘const json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >’ is ambiguous
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:283: note: candidates are: json_spirit::Value_impl<Config>::Value_impl(double) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:275: note: json_spirit::Value_impl<Config>::Value_impl(uint64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:267: note: json_spirit::Value_impl<Config>::Value_impl(int64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:259: note: json_spirit::Value_impl<Config>::Value_impl(int) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:251: note: json_spirit::Value_impl<Config>::Value_impl(bool) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:219: note: json_spirit::Value_impl<Config>::Value_impl(typename Config::String_type::const_pointer) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >] <near match>
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp: In member function ‘void RemoteMinerClient::SendMetaHash(int64, const std::vector<unsigned char, std::allocator<unsigned char> >&, unsigned int, const std::vector<unsigned char, std::allocator<unsigned char> >&, const uint256&, unsigned int)’:
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp:658: error: conversion from ‘long long int’ to ‘const json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >’ is ambiguous
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:283: note: candidates are: json_spirit::Value_impl<Config>::Value_impl(double) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:275: note: json_spirit::Value_impl<Config>::Value_impl(uint64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:267: note: json_spirit::Value_impl<Config>::Value_impl(int64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:259: note: json_spirit::Value_impl<Config>::Value_impl(int) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:251: note: json_spirit::Value_impl<Config>::Value_impl(bool) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:219: note: json_spirit::Value_impl<Config>::Value_impl(typename Config::String_type::const_pointer) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >] <near match>
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp:664: error: conversion from ‘int64’ to ‘const json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >’ is ambiguous
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:283: note: candidates are: json_spirit::Value_impl<Config>::Value_impl(double) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:275: note: json_spirit::Value_impl<Config>::Value_impl(uint64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:267: note: json_spirit::Value_impl<Config>::Value_impl(int64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:259: note: json_spirit::Value_impl<Config>::Value_impl(int) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:251: note: json_spirit::Value_impl<Config>::Value_impl(bool) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:219: note: json_spirit::Value_impl<Config>::Value_impl(typename Config::String_type::const_pointer) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >] <near match>
/home/smark/software/bitcoin-pool/src/remote/remoteminerclient.cpp:667: error: conversion from ‘int64’ to ‘const json_spirit::Value_impl<json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > >’ is ambiguous
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:283: note: candidates are: json_spirit::Value_impl<Config>::Value_impl(double) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:275: note: json_spirit::Value_impl<Config>::Value_impl(uint64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:267: note: json_spirit::Value_impl<Config>::Value_impl(int64_t) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:259: note: json_spirit::Value_impl<Config>::Value_impl(int) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:251: note: json_spirit::Value_impl<Config>::Value_impl(bool) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >]
/home/smark/software/bitcoin-pool/src/remote/../json/json_spirit_value.h:219: note: json_spirit::Value_impl<Config>::Value_impl(typename Config::String_type::const_pointer) [with Config = json_spirit::Config_vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >] <near match>
make[2]: *** [cmake-bitcoinr/CMakeFiles/bitcoinr.dir/__/src/remote/remoteminerclient.cpp.o] Error 1
make[1]: *** [cmake-bitcoinr/CMakeFiles/bitcoinr.dir/all] Error 2
make: *** [all] Error 2
Any idea of what might wrong here? Thanks in advance! Jon. I'm having identical issues trying to compile for an AMD64 server running Debian Lenny. :| |
|
|
|
|
FairUser
Sr. Member
Offline
Activity: 1344
Merit: 264
bit.ly/3QXp3oh | Ultimate Launchpad on TON
|
|
December 05, 2010, 12:39:27 PM |
|
I just notice my bitcoinr log file showed the server was down for a few minutes, and now it shows the additional line:
0 blocks generated since 2010-12-05 12:16:18 UTC
Thanks for the extra info.
However, I've noticed my bitcoinr log also says "Server reports my khash/s as 566" very consistently.
This use to say "Server reports my khash/s as 833" very consistently.
I'm seeing the same behavior accross my 3 boxes I have running bitcoinr.
I'm curious as to what changed on the server side, cause I didn't change a thing on my end and it seems to report less khash/s now than it did before the change.
|
|
|
|
doublec
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
December 05, 2010, 12:43:01 PM |
|
I just notice my bitcoinr log file showed the server was down for a few minutes, and now it shows the additional line:
0 blocks generated since 2010-12-05 12:16:18 UTC
The server stopped for some reason. I've restarted it. However, I've noticed my bitcoinr log also says "Server reports my khash/s as 566" very consistently.
This use to say "Server reports my khash/s as 833" very consistently.
I'm seeing the same behavior accross my 3 boxes I have running bitcoinr.
I'm curious as to what changed on the server side, cause I didn't change a thing on my end and it seems to report less khash/s now than it did before the change.
The khash rate seems to be oscillating for me. It reports 400 khash/s then the next report it's 1600. The average of those 2 is 1,000 which is the normal rate for my cpu. Odd. The total combined khash rate is also oscillating. I think the server is overloaded. It's pegged at a 100% CPU right now with 143 clients. |
|
|
|
|
FairUser
Sr. Member
Offline
Activity: 1344
Merit: 264
bit.ly/3QXp3oh | Ultimate Launchpad on TON
|
|
December 05, 2010, 12:45:57 PM |
|
Scratch that. It seems to have come back around and seems a bit more normal the last few minutes. I just notice my bitcoinr log file showed the server was down for a few minutes, and now it shows the additional line:
0 blocks generated since 2010-12-05 12:16:18 UTC
Thanks for the extra info.
However, I've noticed my bitcoinr log also says "Server reports my khash/s as 566" very consistently.
This use to say "Server reports my khash/s as 833" very consistently.
I'm seeing the same behavior accross my 3 boxes I have running bitcoinr.
I'm curious as to what changed on the server side, cause I didn't change a thing on my end and it seems to report less khash/s now than it did before the change.
|
|
|
|
FairUser
Sr. Member
Offline
Activity: 1344
Merit: 264
bit.ly/3QXp3oh | Ultimate Launchpad on TON
|
|
December 05, 2010, 12:53:10 PM |
|
Yeah, I'm starting to see that too. It's jumping between 433 and 1633 for me.
Should be averaging around 833 typically.
Odd indeed.
|
|
|
|
FairUser
Sr. Member
Offline
Activity: 1344
Merit: 264
bit.ly/3QXp3oh | Ultimate Launchpad on TON
|
|
December 05, 2010, 01:14:59 PM |
|
Status update: Offline again. Traceroute seems fine though.
|
|
|
|
doublec
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
December 05, 2010, 01:19:38 PM |
|
Status update: Offline again. Traceroute seems fine though.
Yep, server died again. I'm looking into it. |
|
|
|
|
FairUser
Sr. Member
Offline
Activity: 1344
Merit: 264
bit.ly/3QXp3oh | Ultimate Launchpad on TON
|
|
December 05, 2010, 01:24:30 PM |
|
You mentioned previously that your server was running 80-100% CPU. Is it possible that there could be too many clients now and the server is just under heavy load?
I saw the number of clients in the 180's earlier with the group doing ~200,000 khash/s.
|
|
|
|
doublec
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
December 05, 2010, 01:27:11 PM |
|
You mentioned previously that your server was running 80-100% CPU. Is it possible that there could be too many clients now and the server is just under heavy load?
I saw the number of clients in the 180's earlier with the group doing ~200,000 khash/s.
Yes, most likely. As a quick workaround I've brought a second server online. If the number of clients on one is greater than 100 I suggest connecting to the second instead. The second server is at IP address 173.255.205.10 so the client command is: remoteminer.exe -server 173.255.205.10 -address abitcoinaddress With 100 on each this will handle current load until I look into the issue. |
|
|
|
|
doublec
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
December 05, 2010, 01:34:15 PM |
|
puddinpop, it'd be great to have a way to set a maximum number of clients and maybe have a message printed to the client trying to connect if that is exceeded. Any thoughts on how to decrease the CPU usage of the server?
|
|
|
|
|
doublec
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
December 05, 2010, 01:48:38 PM |
|
Yes, most likely. As a quick workaround I've brought a second server online. If the number of clients on one is greater than 100 I suggest connecting to the second instead. The second server is at IP address 173.255.205.10 so the client command is:
I've temporarily hacked in a hard coded limit of 102 clients. Any connects after that will fail. Unfortunately no message is printed to the client and it immediately retries but it beats the server crashing. |
|
|
|
|
jon_smark
Member
Offline
Activity: 90
Merit: 10
|
|
December 05, 2010, 03:35:21 PM |
|
So it seems I'm not the only one having trouble compiling the code on an x86_64 platform. Is it a known limitation that the code will only compile on 32-bit architectures? Or has someone managed to get it running on a 64-bit arch?
Cheers,
Jon
|
|
|
|
|
puddinpop (OP)
Member
Offline
Activity: 103
Merit: 17
|
|
December 05, 2010, 06:35:35 PM |
|
I've updated the first post with a new release. As before, the client and server must be at least the ones from 2010-12-02 to work with each other. This release should help alleviate the hash rate fluctuation, especially if it is caused by CPU usage on the server. The CPU usage itself won't be reduced, but it should be more stable. Also, there is an experimental remote CUDA client included in the release. Expect half the hash rate you get with the regular CUDA miner built into the standard client.
Please note that the way to specify options for the remote miner has changed. Now you use = instead of space between the option and the value.
|
|
|
|
doublec
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
December 05, 2010, 11:51:37 PM |
|
I've updated the first post with a new release. As before, the client and server must be at least the ones from 2010-12-02 to work with each other. This release should help alleviate the hash rate fluctuation, especially if it is caused by CPU usage on the server. The CPU usage itself won't be reduced, but it should be more stable. Also, there is an experimental remote CUDA client included in the release. Expect half the hash rate you get with the regular CUDA miner built into the standard client.
Please note that the way to specify options for the remote miner has changed. Now you use = instead of space between the option and the value.
I plan to switch the pool to this version at 5:00 am Monday 6 December UTC. That's 5 hours from the time I posted this. This will require contributers to update the miner software. I'll post here when the switch is done. The server will use the 'contributed' method. |
|
|
|
|
FairUser
Sr. Member
Offline
Activity: 1344
Merit: 264
bit.ly/3QXp3oh | Ultimate Launchpad on TON
|
|
December 06, 2010, 12:50:09 AM |
|
puddinpop, what's the URL we can get this from?
|
|
|
|
doublec
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
December 06, 2010, 12:54:09 AM |
|
puddinpop, what's the URL we can get this from?
puddinpop updated the original post with source and binaries. I've also added it to my git repository in the 'bitcoin-remote-20101205' branch: https://github.com/doublec/bitcoin-poolI've just pushed to master the tweaks to build the miner only code on linux. |
|
|
|
|
doublec
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
December 06, 2010, 03:09:24 AM |
|
I updated the server on 173.255.205.10 early since there were only 4 clients connected. Instructions updated here: http://www.bluishcoder.co.nz/bitcoin-pool/Basically you need the new client binary. The windows version is now called remoteminer-cpu.exe and the arguments to it require '=' instead of a space between the '-address' and its value (and '-server' and its value). There's also a remoteminer-cuda.exe for those with a cuda compatible GPU. Let see how well this handles load. If it's fine I'll take down the other server. |
|
|
|
|
doublec
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
December 06, 2010, 03:25:59 AM |
|
puddinpop, when running this latest version I'm always seeing a message on the remote client saying that my address is not found in the block being solved. It doesn't show the share that I'd get that it used to. Is something broken or is there a change in the behaviour?
|
|
|
|
|
|
