mirror of
https://github.com/google/brotli.git
synced 2026-07-09 02:08:06 +00:00
Fail to build nginx with latest brotli with bazel #233
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @S8Cloud on GitHub (May 31, 2018).
I saw a repository that use bazel to build nginx (along with boringssl & brotli) at google git and I modified just 2 lines to use the latest brotli
It works fine but when I changed it to
It comes with build error:
My system is Ubuntu 18.04 LTS with stable bazel.
@eustas commented on GitHub (May 31, 2018):
Didn't know that there is Bazel build for nginx =)
Going to investigate soon.
@eustas commented on GitHub (May 31, 2018):
I have a simple explanation now: googlesource ngx_brotli differs from github ngx_brotli.
Going to add Bazel WORKSPACE / BUILD to eustas/ngx_brotli soon.
Would appreciate if you close this issue here and create it at eustas/ngx_brotli instead. Thanks!
@S8Cloud commented on GitHub (May 31, 2018):
Actually it can be built successfully with your
eustas/ngx_brotliandold google/brotligithub version as it is just the same asgooglesource brotli.So I think the problem may comes from newer version of google/brotli (github version).
@eustas commented on GitHub (May 31, 2018):
Hmm. Error says that there is problem with golang Bazel plugin. Going to try to update it to the latest version.
@eustas commented on GitHub (May 31, 2018):
Updated golang/JS bazel plugins to latest stable (#676); not sure if this will help; going to try building nginx with newer brotli later.
@S8Cloud commented on GitHub (May 31, 2018):
Changed org_brotli into commit
29dc2cce9090d6c92c908116e11373bc7fdc8ad1@eustas commented on GitHub (May 31, 2018):
Oh, this looks like Bazel issue =( https://github.com/bazelbuild/bazel/issues/2391
In short: if in project A
WORKSPACEsomething is defined, then project B that uses project A have to have same definition inWORKSPACE.At referenced commit
WORKSPACEwas almost empty, justjunitmaven artifact reference. Now it has much more...Going to investigate if there is a way to trick Bazel.
@eustas commented on GitHub (May 31, 2018):
Could you try if #677 works for you?
@S8Cloud commented on GitHub (Jun 1, 2018):
Thank you for your great work, commit
03c34704c98ff62e230e26b5071fe46db97308ebworks well with latest build of bazel!@eustas commented on GitHub (Jun 4, 2018):
Landed PR #677.