-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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 patch repeat application issue #17592
Conversation
dependency on configure should be order-only (after the `|`) since a patch modifies the file. also use CMakeLists.txt since llvm's configure will be going away
No rule to make target CMakeLists.txt in a clean build, my bad
Oops, this breaks from-scratch builds. fix in c31c5f6 |
sigh, this is going to cause a lot of bad builds :( The problem being that CMakeFiles.txt was older than the tgz archive, so we're going to re-extract it on top of the existing files. Then we're mostly not going to patch them, because we think we already did... |
Ah, crap, that's what it was. Makes sense now. Sure would've been nice if you'd reviewed this. I also should have done more extensive local tests. |
Sorry, I had looked at this but missed that. I'll push a hotfix shortly. |
c31c5f6 seems okay but needs people to do |
re-extraction of a tarball doesn't properly re-apply patches for llvm this patch will force everyone to get a rebuild of a properly patched llvm
dependency on configure should be order-only (after the `|`) since a patch modifies the file. also use CMakeLists.txt since llvm's configure will be going away
No rule to make target CMakeLists.txt in a clean build, my bad
re-extraction of a tarball doesn't properly re-apply patches for llvm this patch will force everyone to get a rebuild of a properly patched llvm
dependency on configure should be order-only (after the
|
)since a patch modifies the file. also use CMakeLists.txt since
llvm's configure will be going away
cc @ViralBShah