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

Fix LLVM_CONFIG not be a prerequisite #11509

Conversation

straight-shoota
Copy link
Member

@straight-shoota straight-shoota commented Nov 30, 2021

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 using call makes it more expressive.

Resolves crystal-lang/distribution-scripts#171

@straight-shoota straight-shoota added kind:bug A bug in the code. Does not apply to documentation, specs, etc. topic:infrastructure kind:regression Something that used to correctly work but no longer works labels Nov 30, 2021
Copy link
Member

@sdogruyol sdogruyol left a 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 🙏

@oprypin
Copy link
Member

oprypin commented Nov 30, 2021

With that PR merged and before this one, this is all I saw in my terminal:

\033[33mUsing /usr/bin/llvm-config [version=13.0.0]\033[0m

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.

@straight-shoota
Copy link
Member Author

@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.

@straight-shoota
Copy link
Member Author

Okay, let's revert in #11513 and then I'll resubmit the fixed implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:bug A bug in the code. Does not apply to documentation, specs, etc. kind:regression Something that used to correctly work but no longer works topic:infrastructure
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI fails for newest nightly docker image
4 participants