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
Disable building Proton by default #2362
Conversation
Signed-off-by: Daira Hopwood <daira@jacaranda.org>
d583056
to
b04529f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We must ensure that CI does not pass non-default flags and therefore this PR merge will exercise the default build which should now exclude proton.
then | ||
PROTON_ARG='--enable-proton=no' | ||
PROTON_ARG='' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick: I suspect many users do ./configure …; make; make install
, and I'd like to change the default for them. However, I'm content to rely on the underspecified policy that "build.sh
is the only officially supported build path for Zcash" (despite my desire for #58 eventually).
Note that #2280 should be included in 1.0.9 because it fixes potential build problems for people who do want to build proton. Otherwise they will opt in to build and be confused as to why it doesn't. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK. I'd also like the argument to be inverted in configure.ac
for consistency, but that's a soft requirement.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reviewed CI to verify that it builds with default args (aside from -j
).
@zkbot r+ |
📌 Commit b04529f has been approved by |
⌛ Testing commit b04529f with merge 48fcde310c8457ea73bf7c0bdb8f1fcc66787393... |
💔 Test failed - pr-merge |
Tests failed because I manually cancelled the build, due to a problem with #2174. |
Eh, just clicked 'rebuild' on buildbot. Let's see how homu likes that. |
The answer is Homu does not like that, so: @zkbot retry |
⌛ Testing commit b04529f with merge ab711beedc0a540a593866418385f2a1e83e55a0... |
💔 Test failed - pr-merge |
@zkbot retry (I've confused buildbot by stopping and restarting various builders without regard to their triggering dependencies.) |
⌛ Testing commit b04529f with merge 79283e2509be760ee5b41ba6ddd78db89600dda6... |
💔 Test failed - pr-merge |
@zkbot retry |
…at-least Disable building Proton by default fixes #2361 Signed-off-by: Daira Hopwood <daira@jacaranda.org>
💔 Test failed - pr-merge |
@zkbot retry |
⌛ Testing commit b04529f with merge 80857feb5cdcfa5d61bedd8269678806328c6609... |
💔 Test failed - pr-merge |
Test failed because the builder couldn't access the network parameters. @zkbot retry |
⌛ Testing commit b04529f with merge 74cae51b0ff1433e7b3f3edc58c74e5a59eace6d... |
💔 Test failed - pr-merge |
The very last test failed because the builder didn't have pyzmq installed 😂 @zkbot retry |
…at-least Disable building Proton by default fixes #2361 Signed-off-by: Daira Hopwood <daira@jacaranda.org>
fixes #2361
Signed-off-by: Daira Hopwood daira@jacaranda.org