Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bitcoin] Allow bitcoin to be compiled with optional zmq dependency #23088

Conversation

mecampbellsoup
Copy link
Contributor

Since the 0.12 release of bitcoin, it has been possible to utilize ZMQ for pub-sub messaging to allow bitcoind to communicate with other processes.

The UNIX installation docs list it as an optional dependency: https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md#dependencies

Here are detailed docs in the bitcoin GH repo discussing how to make use of ZMQ.

In particular, ZMQ is needed to facilitate message passing from bitcoind to-and-from lnd. Here are docs from the Lightning team discussing how to wire up bitcoind to communicate with lnd.

@ilovezfs
Copy link
Contributor

Let's require it. No need for an option.

@mecampbellsoup
Copy link
Contributor Author

mecampbellsoup commented Jan 19, 2018

@ilovezfs SGTM. So remove the => :optional flag?

Once that change is made, the compilation process should report yes when checking for ZMQ, correct?

image

Strange that ZMQ isn't found during the build... perhaps not strange at all since I haven't made it a required dependency.

ZMQ not found during build

@ilovezfs
Copy link
Contributor

yup

Options used to compile and link:
  with wallet   = yes
  with gui / qt = no
  with zmq      = yes
  with test     = yes
  with bench    = yes
  with upnp     = yes
  debug enabled = no
  werror        = no

just remove the => :optional

@ilovezfs
Copy link
Contributor

also we should bump the revision here

@mecampbellsoup
Copy link
Contributor Author

@ilovezfs where is the revision set, is that the sha256 macro?

@mecampbellsoup mecampbellsoup force-pushed the add-zmq-support-for-bitcoin-recipe branch from 4cc212e to 1b5334f Compare January 19, 2018 21:03
@ilovezfs
Copy link
Contributor

here's an example 656e549

@mecampbellsoup
Copy link
Contributor Author

Cool, it looks like there's no revision yet in the bitcoin.rb recipe, so just set it to revision 1? Or is it zero-index, i.e. revision 0?

@ilovezfs
Copy link
Contributor

Counting starts from 0 but revision 0 is always left implicit.

@mecampbellsoup
Copy link
Contributor Author

@ilovezfs cool I pushed a commit adding revision 1.

@mecampbellsoup
Copy link
Contributor Author

@ilovezfs hm, build still failing - does this look familiar to you at all?

image

@ilovezfs
Copy link
Contributor

@mecampbellsoup it's this: bitcoin/bitcoin#12009

@ilovezfs
Copy link
Contributor

if you rebase this, it should build now

@mecampbellsoup mecampbellsoup force-pushed the add-zmq-support-for-bitcoin-recipe branch from 6aee3b8 to e62bea1 Compare January 20, 2018 00:00
@@ -11,6 +11,7 @@ class Bitcoin < Formula
patch do
url "https://github.com/bitcoin/bitcoin/commit/1ec0c0a01c31.patch?full_index=1"
sha256 "a1f761fe29f78e783cb4b55f8029900f94b45d1188cb81c80f73347ee2fdc025"
revision 1
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ilovezfs revision inside this patch block, or outside?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should go under homepage in this case

@mecampbellsoup mecampbellsoup force-pushed the add-zmq-support-for-bitcoin-recipe branch from e62bea1 to b98bbfd Compare January 20, 2018 01:01
@fxcoudert
Copy link
Member

Thanks @mecampbellsoup for the pull request and congrats on your first contribution to Homebrew!

@fxcoudert fxcoudert closed this in d5b3e17 Jan 20, 2018
@mecampbellsoup mecampbellsoup deleted the add-zmq-support-for-bitcoin-recipe branch January 21, 2018 15:07
@Homebrew Homebrew locked and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants