-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Windows: bootstrapping broken with Bazel 0.6.0 #3863
Comments
I'm wondering why we didn't see this on CI. |
bazel/src/main/native/windows/build_windows_jni.sh Lines 88 to 92 in b4ebfd7
The culprit is that VSTEMP is an MSYS path under
|
Humm should we do another patch release? Is the bootstrap test running on windows? I remember we had to turn it down waiting for a release but maybe we forgot to readd it. |
/cc @jcater |
Do we know what the fix for this is? If it's still under investigation, I'd like to release 0.6.1 to improve mac users' experience, and then we can do 0.6.2 with the fix for this when we have it. |
I'm working on a fix. There are multiple problems, I already fixed two, there's at least one more. |
Also: - check as the first thing in compile.sh that we can locate the GNU coreutils, and remove the duplicate check for the same thing on Windows - check early in compile.sh that we can access python.exe Fixes #3863 Change-Id: Ib48b405cf93eafd48e21b280bcbab4d45117c1d9 PiperOrigin-RevId: 171291435
Boostrapping from the 0.6.0 dist archive is broken on Windows, because
//src/main/native:jni.h
is a generated file, included from//src/main/native/windows/*
, but not part of the dist archive.The text was updated successfully, but these errors were encountered: