bitcoin: Boost or whatever compilation error
Debian wheezy (yes, old, but that’s it), who succeeded to compile easily some bitcoin shxtty forks, but not bitcoin, incredible…
Maybe related to #13182 or #2998, no idea but starting to be fed up with this stuff, problem with wallet, OK disabling wallet, --disable-wallet then --with-gui=no then --with-incompatible-bdb, what’s next?
Error with the latest option:
libbitcoin_server.a(libbitcoin_server_a-init.o): In function path<boost::filesystem::directory_entry>': /usr/local/include/boost/filesystem/path.hpp:140: undefined reference to
boost::filesystem::path_traits::dispatch(boost::filesystem::directory_entry const&, std::string&)’
libbitcoin_wallet.a(libbitcoin_wallet_a-db.o): In function copy_file': /usr/local/include/boost/filesystem/operations.hpp:497: undefined reference to
boost::filesystem::detail::copy_file(boost::filesystem::path const&, boost::filesystem::path const&, boost::filesystem::detail::copy_option, boost::system::error_code*)’
collect2: error: ld returned 1 exit status
make[2]: *** [bitcoind] Error 1
And config.log here http://www.peersm.com/config.txt
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 15 (8 by maintainers)
Commits related to this issue
- Merge #13982: refactor: use fs:: over boost::filesystem:: 4b3b85c597 refactor: use fs:: over boost::filesystem:: (fanquake) Pull request description: Noticed while investigating #13973. Tree-SHA... — committed to Munkybooty/dash by deleted user 6 years ago
- Merge #13982: refactor: use fs:: over boost::filesystem:: 4b3b85c597 refactor: use fs:: over boost::filesystem:: (fanquake) Pull request description: Noticed while investigating #13973. Tree-SHA... — committed to Munkybooty/dash by deleted user 6 years ago
- Merge #13982: refactor: use fs:: over boost::filesystem:: 4b3b85c597 refactor: use fs:: over boost::filesystem:: (fanquake) Pull request description: Noticed while investigating #13973. Tree-SHA... — committed to Munkybooty/dash by deleted user 6 years ago
- Merge #13982: refactor: use fs:: over boost::filesystem:: 4b3b85c597 refactor: use fs:: over boost::filesystem:: (fanquake) Pull request description: Noticed while investigating #13973. Tree-SHA... — committed to Munkybooty/dash by deleted user 6 years ago
- Merge #13982: refactor: use fs:: over boost::filesystem:: 4b3b85c597 refactor: use fs:: over boost::filesystem:: (fanquake) Pull request description: Noticed while investigating #13973. Tree-SHA... — committed to Munkybooty/dash by deleted user 6 years ago
- Merge #13982: refactor: use fs:: over boost::filesystem:: 4b3b85c597 refactor: use fs:: over boost::filesystem:: (fanquake) Pull request description: Noticed while investigating #13973. Tree-SHA... — committed to Munkybooty/dash by deleted user 6 years ago
- Merge #13982: refactor: use fs:: over boost::filesystem:: 4b3b85c597 refactor: use fs:: over boost::filesystem:: (fanquake) Pull request description: Noticed while investigating #13973. Tree-SHA... — committed to Munkybooty/dash by deleted user 6 years ago
I know that wheezy is eol but happy with it and I am not going to screw up/reinstall everything that is running on it
My question was more: “should I investigate? Wait? If you are aware about of some issues with boost, then please tell it”
Still surprised that I can compile shxtty forks but not bitcoin, it should be the contrary
Currently trying @fanquake commit (if I understand correctly this boost thing is doing very little then should not block the complete process)
Let’s see (I have the Berkeley DB issue too, bypassing it)