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.
Motivation for this change
As pointed out in #84096 llvmPackages still points to llvm 7. This commit changes llvmPackages to llvm 9. I chose not to use llvm 10, since it was just released.
Since boost16x is boost 1.69 using clang >7 should work in most cases (<1.69 needs clang <=7).
This still needs to be tested on darwin! If you can tell me how to test without darwin machine, I'll compile/fix myself.
On linux all packages building before these changes are still building afterwards.
Things done
coreclr
now uses clang found in passed llvmPackages, instead of separate argument to ensure all llvm-tools use the same versionboost
has extra assert to catch compiling boost <1.69 with clang >=8 early on. This combination is not possible, because clang removed a feature.irods
andcoreclr
to llvm 7, since both can not be compiled with newer clang (irods needs boost <1.69 and coreclr has problems with clangs internal assembler after version 8)sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)