Open
Conversation
Crystal 1.11 might not be ready to support LLVM 17 on macOS yet.
Using crystal eval fails because it defaults to dynamic linking, however the libraries needed for dynamic linking aren't present. We could add those libraries but I decided it would be better to try and compile a statically linked crystal program instead.
Collaborator
Author
|
This looks like the culprit for the macOS failures: llvm/llvm-project#78860 |
rbishop
force-pushed
the
static-build-checks
branch
from
4b4d641 to
8177823
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Using crystal eval fails because it defaults to dynamic linking,
however the libraries needed for dynamic linking aren't present. We
could add those libraries but I decided it would be better to try and
compile a statically linked crystal program instead.