just emerge -e =bitcoin-qt-0.12.1 Reproducible: Always
Created attachment 446140 [details] /var/tmp/portage/net-p2p/bitcoin-qt-0.12.1/temp/build.log
Created attachment 446142 [details] emerge --info '=net-p2p/bitcoin-qt-0.12.1::gentoo'
Created attachment 446144 [details] emerge -pqv '=net-p2p/bitcoin-qt-0.12.1::gentoo'
Created attachment 446146 [details] /var/tmp/portage/net-p2p/bitcoin-qt-0.12.1/temp/environment
The same error in bitcoin-0.13.0 libtool: link: x86_64-pc-linux-gnu-g++ -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -pie -Wl,-O1 -o qt/bitcoin-qt qt/qt_bitcoin_qt-bitcoin.o -pthread -Wl,--as-needed qt/libbitcoinqt.a libbitcoin_server.a libbitcoin_wallet.a libbitcoin_cli.a libbitcoin_common.a libbitcoin_util.a libbitcoin_consensus.a crypto/libbitcoin_crypto.a -lunivalue -lleveldb -lmemenv -L/usr/lib64 -lboost_system -lboost_filesystem -lboost_program_options-mt -lboost_thread -lboost_chrono-mt -L/usr/lib64/qt4 -lQtGui -lQtNetwork -lQtDBus -lQtXml -lQtCore -lqrencode -lprotobuf /usr/lib64/libdb_cxx-4.8.so -lpthread -lssl -lcrypto -lminiupnpc -lsecp256k1 -levent_pthreads -levent -lanl -pthread qt/libbitcoinqt.a(qt_libbitcoinqt_a-rpcconsole.o): In function `RPCExecutor::request(QString const&)': rpcconsole.cpp:(.text+0x5760): undefined reference to `UniValue::write(unsigned int, unsigned int) const' rpcconsole.cpp:(.text+0x59cf): undefined reference to `UniValue::get_str() const' rpcconsole.cpp:(.text+0x5c3c): undefined reference to `find_value(UniValue const&, std::string const&)' rpcconsole.cpp:(.text+0x5c8c): undefined reference to `find_value(UniValue const&, std::string const&)' rpcconsole.cpp:(.text+0x5c97): undefined reference to `UniValue::get_str() const'
Looks like you built dev-libs/univalue with C++11 CXXFLAGS, and then removed those CXXFLAGS? I don't think that is supposed to work...
(In reply to Luke-Jr from comment #6) > Looks like you built dev-libs/univalue with C++11 CXXFLAGS, and then removed > those CXXFLAGS? I don't think that is supposed to work... There is an abi incompatibility wrt c++11 between gcc-4.9 and gcc-5. For an explanation of whats going on, see https://blogs.gentoo.org/blueness/2015/03/10/the-c11-abi-incompatibility-problem-in-gentoo/ Since you've moved to gcc-5, the easiest solution at this point is to just switch to that and use only gcc-5, drop 4. I know its not stable yet, but we're close. I'm closing this test-request because I'm pretty sure about what's going on. Please test with gcc-5 and reopen if the problem persists.
