-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
build envoy with bazel,but has error, someone would help me? #13194
Comments
I have the same error, windows10 |
Did you follow this process to set-up your build environment? https://github.com/envoyproxy/envoy/blob/master/bazel/README.md#windows @envoyproxy/windows-dev |
@WestEnlarged @rtttech you will have to Python is installed and on the PATH as described in the linked docs I would also suggest supplying a target to |
@yanavlasov thank you, i forget the the problem has been solved. but the build still failed. It seems MSVS not support the option '-Zc:__cplusplus' , not sure. i was very confused! then i remove this option, got this: |
@WestEnlarged what version of the Windows SDK are you on? You will need a version of Windows that is recent enough to include support for Unix Domain Sockets and an SDK that contains that header, we have tested only with VS 2019 and the associated VS Build Tools standalone installs |
i installed vs2019 and using windows 10 sdk(10.0.19041.0). Then i follow the instructions ( maybe i shoud working without windows. what environment are you using for development? @sunjayBhatia |
From the error message it looks like the 'ninja' is not in the path. In my dev environment I have it separately installed and added on the path. @sunjayBhatia does ninja come with VS build tools 2019 or does it have to be installed separately? |
Looks like theres also a path issue in the CMake output there as well: Ninja comes with VS Build Tools (it is a 32 bit exe so just be aware if you've disabled support for that), just needs to be on your PATH (you can also install it separately if you like but it needs to be on your PATH as described in the setup docs) |
I have recently been using a Windows Server 2019 host in GCP, doing builds in the |
can you give us the output of your environment? Seems like some environment variable may be mangled |
@sunjayBhatia i'm using win10 professional(10.0.18362) the environment variables:
USERDOMAIN=DESKTOP-6KJIBN1
can catch the follow issue and preivious issues:
if i modify those files encoding. it report preivious path issue. all of this. |
After following the build instructions on a clean install VM, here are my relevant env variables for each shell. Note that when following the build instructions for Windows, you only need to set environment variables in the shell that you want to build in. For me, I invoke bazel in cmd, so I only set up the environment variables in a cmd prompt. cmd:
msys:
I can successfully build the envoy binary using: FYI this was done on rsmaster a few weeks ago |
I retried but faild, and give up windows. Instead of windows, I trail run building in Alpine (WSL). I run DESKTOP-6KJIBN1:/mnt/d/code/envoy# ./ci/run_envoy_docker.sh './ci/do_ci.sh bazel.dev' You are in 'detached HEAD' state. You can look around, make experimental If you want to create a new branch to retain commits you create, you may git checkout -b HEAD is now at bebd0b2 http: update header get call (#135) |
that looks like a download error which should be good to retry just a word of warning, we don't explicitly test building Envoy in WSL, it may work but there is not validation in CI or otherwise If youre comfortable with developing in containers, see https://github.com/envoyproxy/envoy/tree/master/ci#on-windows for notes on using the Windows container build image |
@sunjayBhatia yes, i retry sometimes then build success. Thans a lot! |
i'm using win10 ,and installed bazel (3.5.0) , then i checkout the code to build master with the envoy doc. It is very confused like this, and i was installed python.
`PS E:\code\envoy> bazel build
Starting local Bazel server and connecting to it...
INFO: Repository protodoc_pip3 instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule pip_import defined at:
C:/users/admin/_bazel_admin/mr5hobvt/external/rules_python/python/pip.bzl:51:29: in
INFO: Repository kafka_pip3 instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule pip_import defined at:
C:/users/admin/_bazel_admin/mr5hobvt/external/rules_python/python/pip.bzl:51:29: in
INFO: Repository headersplit_pip3 instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule pip_import defined at:
C:/users/admin/_bazel_admin/mr5hobvt/external/rules_python/python/pip.bzl:51:29: in
INFO: Repository configs_pip3 instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule pip_import defined at:
C:/users/admin/_bazel_admin/mr5hobvt/external/rules_python/python/pip.bzl:51:29: in
ERROR: An error occurred during the fetch of repository 'protodoc_pip3':
Traceback (most recent call last):
File "C:/users/admin/_bazel_admin/mr5hobvt/external/rules_python/python/pip.bzl", line 49, column 13, in _pip_import_impl
fail("pip_import failed: %s (%s)" % (result.stdout, result.stderr))
Error in fail: pip_import failed: (Python was not found but can be installed from the Microsoft Store: https://go.microsoft.com/fwlink?linkID=2082640)
INFO: Repository envoy_build_tools instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
C:/users/admin/_bazel_admin/mr5hobvt/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in
INFO: Repository rules_foreign_cc instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
C:/users/admin/_bazel_admin/mr5hobvt/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in
INFO: Repository upb instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
C:/users/admin/_bazel_admin/mr5hobvt/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in
INFO: Repository io_bazel_rules_go instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
C:/users/admin/_bazel_admin/mr5hobvt/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in
INFO: Repository bazel_gazelle instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
C:/users/admin/_bazel_admin/mr5hobvt/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in
INFO: Repository build_bazel_rules_apple instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
C:/users/admin/_bazel_admin/mr5hobvt/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in
INFO: Repository bazel_toolchains instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
C:/users/admin/_bazel_admin/mr5hobvt/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in
INFO: Reading rc options for 'build' from e:\code\envoy.bazelrc:
'build' options: --workspace_status_command=bash bazel/get_workspace_status --experimental_strict_action_env=true --host_force_python=PY3 --action_env=BAZEL_LINKLIBS=-l%:libstdc++.a --action_env=BAZEL_LINKOPTS=-lm --host_javabase=@bazel_tools//tools/jdk:remote_jdk11 --javabase=@bazel_tools//tools/jdk:remote_jdk11 --enable_platform_specific_config --define absl=1 --action_env=CC --action_env=CXX --action_env=LLVM_CONFIG --action_env=PATH --@com_googlesource_googleurl//build_config:system_icu=0 --test_env=HEAPCHECK=normal --test_env=PPROF_PATH
ERROR: @com_googlesource_googleurl//build_config:system_icu :: Error loading option @com_googlesource_googleurl//build_config:system_icu: no such package '@protodoc_pip3//': pip_import failed: (Python was not found but can be installed from the Microsoft Store: https://go.microsoft.com/fwlink?linkID=2082640)`
The text was updated successfully, but these errors were encountered: