istio-ecosystem / wasm-extensions

Contains miscellaneous Wasm extensions for Istio
Apache License 2.0
105 stars 34 forks source link

Build a Wasm Extension with C++ is always failed #62

Open xcbeyond opened 3 years ago

xcbeyond commented 3 years ago

Build according to Develop a Wasm extension with C++,commond bazel build //:example.wasm is failed: ERROR: C:/users/administrator/_bazel_administrator/e2vfoios/external/proxy_wasm_cpp_sdk/toolchain/BUILD:21:10: no such package '@emscripten_toolchain//': The repository '@emscripten_toolchain' could not be resolved and referenced by '@proxy_wasm_cpp_sdk//toolchain:all' ERROR: Analysis of target '//:example.wasm' failed; build aborted: Analysis failed

clarechu commented 3 years ago

+1

INFO: Build options --compilation_mode, --copt, --dynamic_mode, and 2 more have changed, discarding analysis cache.
INFO: Repository emscripten_toolchain instantiated at:
  no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
  /private/var/tmp/_bazel_clare/4757afce3fe6d2b8f1637ef8fd7c8b38/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in <toplevel>
INFO: Repository 'emscripten_toolchain' used the following cache hits instead of downloading the corresponding file.
 * Hash 'ce7a5c76e8b425aca874cea329fd9ac44b203b777053453b6a37b4496c5ce34f' for https://github.com/emscripten-core/emsdk/archive/2.0.7.tar.gz
If the definition of 'emscripten_toolchain' was updated, verify that the hashes were also updated.
ERROR: An error occurred during the fetch of repository 'emscripten_toolchain':
   Traceback (most recent call last):
    File "/private/var/tmp/_bazel_clare/4757afce3fe6d2b8f1637ef8fd7c8b38/external/bazel_tools/tools/build_defs/repo/http.bzl", line 121, column 10, in _http_archive_impl
        patch(ctx)
    File "/private/var/tmp/_bazel_clare/4757afce3fe6d2b8f1637ef8fd7c8b38/external/bazel_tools/tools/build_defs/repo/utils.bzl", line 161, column 21, in patch
        fail("Error applying patch command %s:\n%s%s" %
Error in fail: Error applying patch command ./emsdk install 2.0.7:
Installing SDK 'sdk-releases-upstream-d7a29d82b320e471203b69d43aaf03b560eedc54-64bit'..
Installing tool 'node-12.18.1-64bit'..
Installation failed!
Error: Downloading URL 'https://storage.googleapis.com/webassembly/emscripten-releases-builds/deps/node-v12.18.1-darwin-x64.tar.gz': <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1045)>
Warning: Possibly SSL/TLS issue. Update or install Python SSL root certificates (2048-bit or greater) supplied in Python folder or https://pypi.org/project/certifi/ and try again.
ERROR: /private/var/tmp/_bazel_clare/4757afce3fe6d2b8f1637ef8fd7c8b38/external/proxy_wasm_cpp_sdk/toolchain/BUILD:21:10: @proxy_wasm_cpp_sdk//toolchain:all depends on @emscripten_toolchain//:all in repository @emscripten_toolchain which failed to fetch. no such package '@emscripten_toolchain//': Error applying patch command ./emsdk install 2.0.7:
Installing SDK 'sdk-releases-upstream-d7a29d82b320e471203b69d43aaf03b560eedc54-64bit'..
Installing tool 'node-12.18.1-64bit'..
Installation failed!
Error: Downloading URL 'https://storage.googleapis.com/webassembly/emscripten-releases-builds/deps/node-v12.18.1-darwin-x64.tar.gz': <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1045)>
Warning: Possibly SSL/TLS issue. Update or install Python SSL root certificates (2048-bit or greater) supplied in Python folder or https://pypi.org/project/certifi/ and try again.
ERROR: Analysis of target '//extensions/basic_auth:basic_auth.wasm' failed; build aborted: Analysis failed
INFO: Elapsed time: 0.898s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded, 117 targets configured)
xcbeyond commented 2 years ago

bazel build //:example.wasm

INFO: Repository proxy_wasm_cpp_sdk instantiated at: /root/wasm-extensions/example/WORKSPACE:9:13: in Repository rule http_archive defined at: /root/.cache/bazel/_bazel_root/63a0e009c06f1f08983230e0fb3c8356/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in WARNING: Download from https://github.com/proxy-wasm/proxy-wasm-cpp-sdk/archive/fd0be8405db25de0264bdb78fae3a82668c03782.tar.gz failed: class java.io.IOException connect timed out ERROR: An error occurred during the fetch of repository 'proxy_wasm_cpp_sdk': Traceback (most recent call last): File "/root/.cache/bazel/_bazel_root/63a0e009c06f1f08983230e0fb3c8356/external/bazel_tools/tools/build_defs/repo/http.bzl", line 111, column 45, in _http_archive_impl download_info = ctx.download_and_extract( Error in download_and_extract: java.io.IOException: Error downloading [https://github.com/proxy-wasm/proxy-wasm-cpp-sdk/archive/fd0be8405db25de0264bdb78fae3a82668c03782.tar.gz] to /root/.cache/bazel/_bazel_root/63a0e009c06f1f08983230e0fb3c8356/external/proxy_wasm_cpp_sdk/temp504676285066786809/fd0be8405db25de0264bdb78fae3a82668c03782.tar.gz: connect timed out ERROR: Error fetching repository: Traceback (most recent call last): File "/root/.cache/bazel/_bazel_root/63a0e009c06f1f08983230e0fb3c8356/external/bazel_tools/tools/build_defs/repo/http.bzl", line 111, column 45, in _http_archive_impl download_info = ctx.download_and_extract( Error in download_and_extract: java.io.IOException: Error downloading [https://github.com/proxy-wasm/proxy-wasm-cpp-sdk/archive/fd0be8405db25de0264bdb78fae3a82668c03782.tar.gz] to /root/.cache/bazel/_bazel_root/63a0e009c06f1f08983230e0fb3c8356/external/proxy_wasm_cpp_sdk/temp504676285066786809/fd0be8405db25de0264bdb78fae3a82668c03782.tar.gz: connect timed out ERROR: no such package '@proxy_wasm_cpp_sdk//bazel/dep': java.io.IOException: Error downloading [https://github.com/proxy-wasm/proxy-wasm-cpp-sdk/archive/fd0be8405db25de0264bdb78fae3a82668c03782.tar.gz] to /root/.cache/bazel/_bazel_root/63a0e009c06f1f08983230e0fb3c8356/external/proxy_wasm_cpp_sdk/temp504676285066786809/fd0be8405db25de0264bdb78fae3a82668c03782.tar.gz: connect timed out INFO: Elapsed time: 74.668s INFO: 0 processes. FAILED: Build did NOT complete successfully (0 packages loaded)

@mark8s Problem accessing githuh network

mark8s commented 2 years ago

@xcbeyond I just found out

mark8s commented 2 years ago

Build completed successfully , My OS is Ubuntu,Bazelisk version: v1.11.0

INFO: Elapsed time: 767.543s, Critical Path: 66.91s INFO: 6 processes: 1 internal, 5 linux-sandbox. INFO: Build completed successfully, 6 total actions