Open Roberto-Gentili opened 9 months ago
It's broken for x64 as well. Seems the latest MinGW (13.1.0) has removed this file. I'm about to try
with:
static: 0
which should tell the Action to no longer attempt to remove this file.
Even if this works, the Action should be fixed.
It's broken for x64 as well. Seems the latest MinGW (13.1.0) has removed this file. I'm about to try
Even with this:
... It does not work:
Also broken for me; tracking this thread.
I solved by using an old compiler version:
... We should do some experiments to understand which version is the latest working one
Version 12.2.0 works.
Version 13.1.0 was released on 17th of September and broke the builds:
No idea what changed in that release, because the MinGW team stopped tagging releases and updating the Changelog two major versions ago... (https://www.mingw-w64.org/changelog/)
In any case, pinning to 12.2.0 is a workaround for now.
It's broken for x64 as well. Seems the latest MinGW (13.1.0) has removed this file. I'm about to try
Even with this:
... It does not work
The error is different though, no longer about pthreads
.
Line |
18 | $exe_path = (Get-Command $Exe).Path
| ~~~~~~~~~~~~~~~~
| The term 'i686-w64-mingw32-gcc' is not recognized as a name of a cmdlet, function, script file, or executable
| program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
| again.
Confirming 12.2.0 works for me, thanks @V0ldek
According to the maintainer of the Chocolatey listing for Mingw, the Chocolatey install method was changed for 13.1.0 due to a few reasons: http://disq.us/p/2w5c5tj
Unfortunately this involved a change in the location of the install directory, leading to the issue with libpthread
being missing.
The plugin now no longer works on x86 and throws this exception:
Here the workflow