{"action":"created","issue":{"url":"https://api.github.com/repos/libbitcoin/libbitcoin-explorer/issues/251","labels_url":"https://api.github.com/repos/libbitcoin/libbitcoin-explorer/issues/251/labels{/name}","comments_url":"https://api.github.com/repos/libbitcoin/libbitcoin-explorer/issues/251/comments","events_url":"https://api.github.com/repos/libbitcoin/libbitcoin-explorer/issues/251/events","html_url":"https://github.com/libbitcoin/libbitcoin-explorer/issues/251","id":85450742,"number":251,"title":"Generate and work wth testnet addresses","user":{"login":"venzen","id":6916056,"avatar_url":"https://avatars.githubusercontent.com/u/6916056?v=3","gravatar_id":"","url":"https://api.github.com/users/venzen","html_url":"https://github.com/venzen","followers_url":"https://api.github.com/users/venzen/followers","following_url":"https://api.github.com/users/venzen/following{/other_user}","gists_url":"https://api.github.com/users/venzen/gists{/gist_id}","starred_url":"https://api.github.com/users/venzen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/venzen/subscriptions","organizations_url":"https://api.github.com/users/venzen/orgs","repos_url":"https://api.github.com/users/venzen/repos","events_url":"https://api.github.com/users/venzen/events{/privacy}","received_events_url":"https://api.github.com/users/venzen/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/libbitcoin/libbitcoin-explorer/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-06-05T06:28:45Z","updated_at":"2015-06-05T17:45:35Z","closed_at":null,"body":"Is there a way to create and manipulate testnet addresses (starting with 'm' character) via BX ?\r\n\r\nI compiled for testnet and have set the network option in the config file."},"comment":{"url":"https://api.github.com/repos/libbitcoin/libbitcoin-explorer/issues/comments/109376565","html_url":"https://github.com/libbitcoin/libbitcoin-explorer/issues/251#issuecomment-109376565","issue_url":"https://api.github.com/repos/libbitcoin/libbitcoin-explorer/issues/251","id":109376565,"user":{"login":"evoskuil","id":1369335,"avatar_url":"https://avatars.githubusercontent.com/u/1369335?v=3","gravatar_id":"","url":"https://api.github.com/users/evoskuil","html_url":"https://github.com/evoskuil","followers_url":"https://api.github.com/users/evoskuil/followers","following_url":"https://api.github.com/users/evoskuil/following{/other_user}","gists_url":"https://api.github.com/users/evoskuil/gists{/gist_id}","starred_url":"https://api.github.com/users/evoskuil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/evoskuil/subscriptions","organizations_url":"https://api.github.com/users/evoskuil/orgs","repos_url":"https://api.github.com/users/evoskuil/repos","events_url":"https://api.github.com/users/evoskuil/events{/privacy}","received_events_url":"https://api.github.com/users/evoskuil/received_events","type":"User","site_admin":false},"created_at":"2015-06-05T17:45:35Z","updated_at":"2015-06-05T17:45:35Z","body":"The readme states:\r\n```\r\nLibbitcoin requires a C++11 compiler, currently minimum GCC 4.8.0 or Clang based on LLVM 3.5.\r\n```\r\nIf you have this you have a sufficient version of Linux. The same document also states that you need to:\r\n```\r\n$ sudo apt-get install build-essential autoconf automake libtool pkg-config\r\n```\r\nAnd that you need to:\r\n```\r\n$ sudo apt-get install libboost-all-dev\r\n```\r\nI'm not sure hat you mean by, \"the boost-library won't build\". The error isn't a boost build error, it's a boost discovery error.\r\n\r\nThe above log indicates a problem with boost. Note that the boost m4 script misrepresents failures. There is typically a \"yes\" and then a failure on the next component, where the failure really applies to the previous component. But in any case, you need to verify your boost installation. Alternatively you can have the installer build boost (more below).\r\n\r\nThe install script is meant to provide a full working install, not to patch up the various parts of the build you may have already installed. The install script is the same that we use for pull and push testing in Travis. It's designed for predictability, not for speed. If you want incremental build and install of the various dependencies, then don't use the script.\r\n\r\nIt works best if you isolate it to a `--prefix=<directory>`, let it build boost using `--build-boost`, and use static linking via `--disable-shared`. This prevents libtool from reaching outside of the prefix directory to use dynamic versions of boost (and ICU as applicable). This will ensure a reliable build as it will have only trivial dependencies on platform shared libraries.\r\n\r\n"}}