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.
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
crystal: 1.2 -> 1.7 #195606
crystal: 1.2 -> 1.7 #195606
Changes from 16 commits
e0d0d1c
9b6172a
ffa22c6
89dab4d
4bd897e
b8ae9f9
ce5ce4b
8a4536c
b1be734
5564346
392df0c
159ddb5
eab3f4d
23b9200
3efc4e5
44073f6
a979bd9
f29f0d0
796afea
52c3f58
3597e7e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 guess we no longer need to do this as you're patching the versions that do not support it.
Otherwise good to. Once this is reinstated I'll squash and merge.
Thanks a ton @GeopJr !!!
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.
The release flag moved to
makeFlags
(which has the same effect as far as I am aware) from the #173928 PR. Is there another reason to include it inFLAGS
?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.
Something I don't get from the x86-darwing error is that it refers to clang-11, but shouldn't it refer to clang-13?
Maybe we could try sticking with llvmPackages_11 here? I'm not sure for the underlying reason, but the llvm package in nixpkgs points to 11.
Or we are missing some path to use llvmPackages_13.clang
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.
:/ Closest discussion I could find: https://discourse.nixos.org/t/nixpkgs-aarch64-darwin-build-m1-uses-wrong-old-clang-how-to-fix/ (in our case x86_64 instead of aarch64)
the suggested change adds clang-unwrapped to PATH
nixpkgs/pkgs/build-support/libredirect/default.nix
Lines 35 to 49 in 6de1617
Someone on darwin needs to give it a try otherwise I'll just revert to llvmPackages_11 for x86_64
The nix build definitely downloaded clang-13: