-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Bazel, Windows: Bazel 0.23.1 no longer works when users don't have VC installed #7661
Labels
area-Windows
Windows-specific issues and feature requests
P1
I'll work on this now. (Assignee required)
platform: windows
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: bug
Comments
meteorcloudy
added
type: bug
P1
I'll work on this now. (Assignee required)
platform: windows
release blocker
area-Windows
Windows-specific issues and feature requests
labels
Mar 7, 2019
Is it a regression from 0.22 to 0.23? If so, we might want to cherrypick it. |
Yes, the fix is coming soon. |
Closed
laurentlb
pushed a commit
that referenced
this issue
Mar 7, 2019
Fixes #7661 RELNOTES: None PiperOrigin-RevId: 237246257
laurentlb
pushed a commit
that referenced
this issue
Mar 7, 2019
Fixes #7661 RELNOTES: None PiperOrigin-RevId: 237246257
katre
pushed a commit
that referenced
this issue
Mar 7, 2019
Fixes #7661 RELNOTES: None PiperOrigin-RevId: 237246257
katre
pushed a commit
that referenced
this issue
Mar 7, 2019
Fixes #7661 RELNOTES: None PiperOrigin-RevId: 237246257
katre
pushed a commit
that referenced
this issue
Mar 8, 2019
Fixes #7661 RELNOTES: None PiperOrigin-RevId: 237246257
katre
pushed a commit
that referenced
this issue
Mar 13, 2019
Fixes #7661 RELNOTES: None PiperOrigin-RevId: 237246257
katre
pushed a commit
that referenced
this issue
Mar 19, 2019
Fixes #7661 RELNOTES: None PiperOrigin-RevId: 237246257
philwo
added
the
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
label
Jun 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-Windows
Windows-specific issues and feature requests
P1
I'll work on this now. (Assignee required)
platform: windows
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: bug
To reproduce with Bazel 0.23.1, you can run the following command without VC installed (or if you do you can do
SET BAZEL_VC=C:/foo/bar/VC
first)You'll get
This happens after we migrated CROSSTOOL definition to Starlark and CROSSTOOL in Starlark is more strict than CROSSTOOL in proto, these must not be empty:
I'll send a fix and add a test for this case.
The text was updated successfully, but these errors were encountered: