Peter Maydell writes:
> On Fri, 16 Feb 2024 at 11:29, Alex Bennée wrote:
>>
>> Peter Maydell writes:
>>
>> > When msys2 updated their libusb packages to libusb 1.0.27, they
>> > dropped support for building them for mingw32, leaving only mingw64
>> > packages. This broke our CI job, as the 'pa
On Fri, 16 Feb 2024 at 11:29, Alex Bennée wrote:
>
> Peter Maydell writes:
>
> > When msys2 updated their libusb packages to libusb 1.0.27, they
> > dropped support for building them for mingw32, leaving only mingw64
> > packages. This broke our CI job, as the 'pacman' package install now
> > fa
Peter Maydell writes:
> When msys2 updated their libusb packages to libusb 1.0.27, they
> dropped support for building them for mingw32, leaving only mingw64
> packages. This broke our CI job, as the 'pacman' package install now
> fails with:
>
> error: target not found: mingw-w64-i686-libusb
>
15.02.2024 18:50, Peter Maydell пишет:
When msys2 updated their libusb packages to libusb 1.0.27, they
dropped support for building them for mingw32, leaving only mingw64
packages. This broke our CI job, as the 'pacman' package install now
fails with:
error: target not found: mingw-w64-i686-lib
On 15/2/24 16:50, Peter Maydell wrote:
When msys2 updated their libusb packages to libusb 1.0.27, they
dropped support for building them for mingw32, leaving only mingw64
packages. This broke our CI job, as the 'pacman' package install now
fails with:
error: target not found: mingw-w64-i686-lib
When msys2 updated their libusb packages to libusb 1.0.27, they
dropped support for building them for mingw32, leaving only mingw64
packages. This broke our CI job, as the 'pacman' package install now
fails with:
error: target not found: mingw-w64-i686-libusb
error: target not found: mingw-w64-i6
