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

can't build the filter by following the instruction on this repo #32

Open
timxi opened this issue Mar 12, 2019 · 4 comments
Open

can't build the filter by following the instruction on this repo #32

timxi opened this issue Mar 12, 2019 · 4 comments

Comments

@timxi
Copy link

timxi commented Mar 12, 2019

@talnordan @yuval-k do you know how to build this filter?

@talnordan
Copy link
Contributor

The README suggests running the following command:

$ bazel build //:envoy

Are you getting an error when running it? If so, can you paste the error output?

@timxi
Copy link
Author

timxi commented Mar 13, 2019

Starting local Bazel server and connecting to it...
... still trying to connect to local Bazel server after 10 seconds ...
ERROR: /opt/git/envoy-filter/envoy-consul-connect/WORKSPACE:8:1: name 'http_archive' is not defined
ERROR: Error evaluating WORKSPACE file
ERROR: error loading package '': Encountered error while reading extension file 'bazel/repositories.bzl': no such package '@envoy//bazel': error loading package 'external': Could not load //external package
ERROR: error loading package '': Encountered error while reading extension file 'bazel/repositories.bzl': no such package '@envoy//bazel': error loading package 'external': Could not load //external package
INFO: Elapsed time: 17.474s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)

@timxi
Copy link
Author

timxi commented Mar 13, 2019

Build label: 0.23.0-homebrew
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Wed Feb 27 11:03:45 2019 (1551265425)
Build timestamp: 1551265425
Build timestamp as int: 1551265425

@talnordan
Copy link
Contributor

The cause of this issue is a backward incompatibility issue in Bazel, which prevents the existing WORKSPACE file from being used with newer Bazel versions.
See https://docs.bazel.build/versions/master/skylark/backward-compatibility.html#remove-native-http-archive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants