-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Be gentler in setting BinaryBuilder makevars #32044
Conversation
Many users have expressed the frustration that setting `USE_BINARYBUILDER=0` in `Make.user` doesn't take; this is because the initializations here should have been `?=` (e.g. "set unless already set") instead of `:=` (e.g. "set immediately"). This remedies that.
Co-Authored-By: Valentin Churavy <vchuravy@users.noreply.github.com>
|
||
# Use the Assertions build | ||
BINARYBUILDER_LLVM_ASSERTS := 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unrelated, but shouldn't this just look at the LLVM_ASSERTIONS
variable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably? @vchuravy is that just a silly oversight on my part?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I originally had it split out to make switching more explicit. No strong feelings on my part.
We don't actually have an asserts build to download (yet)
I've thought this would be good to change for a long time. Would also be good to change any other variables that can be set in Make.user to configure the build process so that |
Will address the LLVM_ASSETS stuff in a future PR. |
Many users have expressed the frustration that setting
USE_BINARYBUILDER=0
inMake.user
doesn't take; this is because the initializations here should have been?=
(e.g. "set unless already set") instead of:=
(e.g. "set immediately"). This remedies that.