MSYS2 Dash Azure Workaround #134
Closed
Conversation
This file contains 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
|
Right, This is just another mingw bug caused by alex. Hopefully it will remedy itself in week or so. So I would just leave it alone for now |
|
Closing because it was already automatically fixed, even though that workaround fixed it too. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a small workaround to fix the broken MinGW32 and MinGW64 builds on our Azure CI right now.
I tried the safer fix mentioned, but it didn't work, so I had to go with the filesystem hack.
msys2/MSYS2-packages#2021
It's probably not worth merging this because anybody who does a fresh install of MSYS2 and then ENIGMA might have this problem anyway? @fundies ?