-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fix LLVM_CONFIG
not be a prerequisite
#11509
Fix LLVM_CONFIG
not be a prerequisite
#11509
Conversation
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.
Thank you @straight-shoota 🙏
With that PR merged and before this one, this is all I saw in my terminal:
With this PR I still see the message garbled like that (so not all is good, still!), but at least it works. Please reconsider forward-fixing and instead consider directly reverting. And reverts should be much quicker to approve and merge, too. |
@oprypin Yeah, I agree we should prefer doing a quick revert first, as soon as an issue is discovered. At least when it has practical impact like this one which has made nightly builds unusable. We might be less aggressive on issues that only break our CI, for example. I'll fix the escape sequence interpretation in a separate PR. |
Okay, let's revert in #11513 and then I'll resubmit the fixed implementation. |
https://github.com/crystal-lang/crystal/pull/11454/files was wrong in making
LLVM_CONFIG
a phony prerequisite because that means it triggers all dependent targets every time. This even causes nightly builds to fail (crystal-lang/distribution-scripts#171).This patch changes the
LLVM_CONFIG
check to a function that's only run once. I think it could even be just a normal variable, but I feel usingcall
makes it more expressive.Resolves crystal-lang/distribution-scripts#171