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

Error with Bazel 6 on Windows #1153

Open
jfirebaugh opened this issue Dec 20, 2022 · 5 comments
Open

Error with Bazel 6 on Windows #1153

jfirebaugh opened this issue Dec 20, 2022 · 5 comments

Comments

@jfirebaugh
Copy link
Contributor

CI fails on Windows when using Bazel 6.0.0:

[3 / 7] Compiling hello-world/hello-world.cc; 1s local ... (2 actions, 1 running)
ERROR: C:/users/circleci/project/bazel/hello-world/BUILD:4:10: Compiling hello-world/hello-world.cc failed: (Exit 2): emcc.bat failed: error executing command (from target //hello-world:hello-world) emscripten_toolchain\emcc.bat --sysroot=external/emscripten_bin_win/emscripten/cache/sysroot -fdiagnostics-color -fno-exceptions -fno-strict-aliasing -funsigned-char -no-canonical-prefixes -std=gnu++17 ... (remaining 27 arguments skipped)
The system cannot find the path specified.
C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\python.exe: can't open file '\emcc.py': [Errno 2] No such file or directory
Target //hello-world:hello-world-wasm failed to build

https://app.circleci.com/pipelines/github/emscripten-core/emsdk/1787/workflows/1e0d2a16-3e9c-42fc-bcfc-46adce0b19a9/jobs/10060

@sbc100
Copy link
Collaborator

sbc100 commented Jan 3, 2023

Do you know when this started happening? Was it a change in this repo that caused it or some external change in bazel?

@sbc100
Copy link
Collaborator

sbc100 commented Jan 3, 2023

If there is no quick for this I think we should perhaps disable that test in CI since its blocking all other changes here.

@jfirebaugh
Copy link
Contributor Author

I believe it started when 6.0.0 was released and picked up the CI pipeline.

#1151 includes a workaround (pinning the Windows build to 5.4.0). If you like I can extract that to a separate PR.

@sbc100
Copy link
Collaborator

sbc100 commented Jan 3, 2023

I believe it started when 6.0.0 was released and picked up the CI pipeline.

#1151 includes a workaround (pinning the Windows build to 5.4.0). If you like I can extract that to a separate PR.

Actually that would be great yes!

@jfirebaugh
Copy link
Contributor Author

#1163

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