-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Update MinGW on Windows 2022 #5729
Conversation
Previously, the GitHub virtual environments only had MinGW v8.1.0 installed. That version was released in October of 2018 and, since then, MinGW has released versions all the way up to v11.2.0. This change updates the MinGW version to the latest available on Chocolatey for the Windows 2022 environment. Windows 2019 retains the current v8.1.0 version. Fixes actions#5530.
cc: @miketimofeev, @igorboskovic3; not sure what the correct flow is to merge this kind of PR so some help is appreciated. I don't believe this requires a new test (but you tell me) and I don't really have a great way to test this locally in any case so I'm hoping that the CI tests cover this change (?). |
images/win/Windows2022-Readme.md
Outdated
@@ -69,7 +69,7 @@ | |||
- Kind 0.14.0 | |||
- Kubectl 1.24.1 | |||
- Mercurial 5.0 | |||
- Mingw-w64 8.1.0 | |||
- Mingw-w64 11.2.0-07112021 |
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.
@abrown no need to update the readme. It is autogenerated
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.
Ok, I reverted that commit. Can you approve the CI run?
This reverts commit cb7a72f.
/azp run windows2019, windows2022 |
Azure Pipelines successfully started running 2 pipeline(s). |
@miketimofeev, I looked at the build error but I couldn't make much sense of it. |
@abrown , You should fix this function to parse correct the mingw version: https://github.com/actions/virtual-environments/blob/78d8bca4d39f7b8be4449f1c331dc66532e9d2b1/images/win/scripts/SoftwareReport/SoftwareReport.Tools.psm1#L105 |
Ok, here is the current string when I install the latest version of MinGW using chocolatey:
This means that reducing the |
/azp run windows2019, windows2022 |
Azure Pipelines successfully started running 2 pipeline(s). |
Now that actions/runner-images#5729 has merged, GitHub runners using `windows-latest` (i.e., Windows 2022) should have a later version of MinGW (i.e., 11.2.0) that solves the build issues observed in this repository. Recall that the `strnlen_s` function is not available on older versions of MinGW but was necessary to compile the C library. With this change, CI will use GitHub's MinGW version instead of manually installing a new one.
Now that actions/runner-images#5729 has merged, GitHub runners using `windows-latest` (i.e., Windows 2022) should have a later version of MinGW (i.e., 11.2.0) that solves the build issues observed in this repository. Recall that the `strnlen_s` function is not available on older versions of MinGW but was necessary to compile the C library. With this change, CI will use GitHub's MinGW version instead of manually installing a new one.
Hello. Did somebody catch the issue with run of C++ application made by recently updated MinGW at the Windows virtual environment? It required some of libraries from MinGW bin directory and set it to the PATH will not help for some reason.
While reproduce the environment locally I detected - that choco adding path to bin at the PATH environment only for the user who install it. So if another user used to run pipeline – adding path to folder with libraries (libstdc++-6.dll and libgcc_s_seh-1.dll) that required to run C++ application will be enough. I added such path while pipeline run - at local environment it help, for remote - no. Probably there is an conflict with another folder from PATH environment, where file(s) with same name(s) may be provided, so directly copying of that libraries to the directory with executable will help with searching of correct version of dll files. Thank you. P.S.
|
Description
Previously, the GitHub virtual environments only had MinGW v8.1.0
installed. That version was released in October of 2018 and, since then,
MinGW has released versions all the way up to v11.2.0. This change
updates the MinGW version to the latest available on Chocolatey for the
Windows 2022 environment. Windows 2019 retains the current v8.1.0
version. Fixes #5530.
Related issue:
Check list